Oromi Agent Services — MCP Server

Agent readability score

Strengths

• Tool names are highly descriptive and domain-specific (e.g., 'uk_business_food_hygiene')
• Descriptions explicitly state use cases (e.g., 'helping a user name a new business')
• Comprehensive coverage of UK-specific data and verification tools

Weaknesses

• Some tool names are generic (e.g., 'web_extract' vs 'web_pdf_extract')
• Input parameter schemas and required/optional fields are not explicitly documented
• Minor functional overlap between 'uk_property_price_trends' and 'uk_property_market_summary'

• web_extract — Similar to 'web_pdf_extract' but lacks clear differentiation in scope
• uk_property_price_trends — Overlaps with 'uk_property_market_summary' in property data context
• util_validate_json — No explicit mention of required/optional parameters in description

Verdict

The toolset excels in clear naming and use-case alignment, with strong domain-specific coverage. Minor improvements in parameter documentation and reducing functional overlap would enhance usability, but the current 85/100 score is justified by its comprehensive, well-structured approach to UK data and verification services.

9/11/2026, 6:03:50 AM

Event narrative

Server transitioned from 'auth-gated' to 'legacy' era with compliance score improving from null to 100.

Risk: medium

• 2026-09-10T21:16:35.016Z — Era changed to 'auth-gated' · Agent moved to auth-gated mode with no compliance score
• 2026-09-11T05:44:28.819Z — Era changed to 'legacy' and compliance score set to 100 · Agent now in legacy mode with full compliance

Advice

Monitor the server's compliance score to ensure sustained performance. Verify that the transition to legacy mode is intentional and aligns with operational goals. Check for any potential issues related to the era change that might affect service reliability.