Skip to main content
Glama
stefanoamorelli

Companies House MCP Server

advanced_company_search

Perform advanced searches for UK companies using multiple filters such as name, status, type, incorporation date, and location to find specific company records.

Instructions

Advanced search for companies with multiple filters

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
locationNoLocation
sic_codesNoSIC codes (comma separated)
start_indexNoStarting index for pagination
company_nameNoCompany name to search for
company_typeNoCompany type
dissolved_toNoDissolved to date (YYYY-MM-DD)
company_numberNoCompany number to search for
company_statusNoCompany status (active, dissolved, etc.)
dissolved_fromNoDissolved from date (YYYY-MM-DD)
items_per_pageNoNumber of results per page (1-100)
company_subtypeNoCompany subtype
incorporated_toNoIncorporated to date (YYYY-MM-DD)
incorporated_fromNoIncorporated from date (YYYY-MM-DD)
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations provided. The description does not disclose behavioral traits such as read-only nature, authentication needs, rate limits, or side effects. For a search tool, it fails to state whether it returns list or aggregates.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single concise sentence, but it omits critical details. It is not verbose, but the brevity sacrifices clarity and completeness.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With 13 optional parameters and no output schema, the description is too sparse. It does not explain how filters combine, pagination behavior, or expected output format, leaving significant gaps for an agent.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% with each parameter having a minimal description. The tool description adds no extra meaning beyond the schema. Baseline 3 is appropriate as the schema does the work.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool performs an 'advanced search for companies', which is specific. However, it does not differentiate from sibling tools like 'search_companies' or 'alphabetical_search', missing details on what makes this search advanced.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance on when to use this tool versus alternatives. With sibling tools like 'search_companies', the description lacks criteria for choosing this advanced search over simpler ones.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/stefanoamorelli/companies-house-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server