Get UK company filing history (most recent first) — accounts, confirmation statements, insolvency events. Source: Companies House (UK).
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Max filings to return (default 10) | |
| number | Yes | UK company number (e.g. 00002078) |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the burden. It adds useful behavioral traits: results are sorted most recent first, and it covers specific filing categories. However, it doesn't mention default limit behavior or potential errors, though 'Get' reasonably implies a read-only operation.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, front-loaded sentence with no wasted words. It efficiently communicates purpose, content, ordering, and source.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple two-parameter tool, the description is sufficiently complete. It covers purpose, content, and ordering, but since there is no output schema, a bit more detail about the response structure could be helpful. Still, it is adequate for understanding and invoking the tool.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The schema already describes both parameters fully (limit with default, number with example). The description adds no additional parameter details, which is acceptable since schema coverage is 100%.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool returns UK company filing history, lists example filing types (accounts, confirmation statements, insolvency events), specifies ordering (most recent first), and identifies the data source. This distinguishes it from sibling tools like uk_company_officers or uk_company_charges.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides clear context: it's for a specific company's filings, not a general search (unlike search_filings). It doesn't explicitly state when not to use it or name alternatives, but the focused scope and source make the intended use obvious.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Several tool groups have overlapping purposes: fda_drug_labels vs health_drug_search, fda_recalls vs health_recalls, fx_official_rates vs treasury_fx_rates, treasury_debt vs us_debt_current, and get_gdp vs get_bea_gdp. These near-duplicates create real ambiguity for an agent deciding which tool to call.
Names mix verb-led styles (get_, search_, compare_, screen_) with domain-led styles (fx_, treasury_, uk_, health_, eurostat_, datausa_). Within the same domain, similar actions use different patterns (get_gdp vs eurostat_gdp vs imf_indicator), making the set feel inconsistent and hard to predict.
75 tools is extreme for any MCP server, especially when many tools are redundant or cover unrelated domains (weather, earthquakes, scholarly search, air quality) outside the stated SEC/economics/demographics/FX focus. This overwhelms agents and burdens context windows.
Core domains like SEC financials, major economic indicators, basic demographics, and current FX rates are well covered. However, gaps remain: no historical FX rates, no stock price/quote tool, limited demographic breakdowns, and no ability to fetch full SEC filing text. Some operations end in dead ends.