Skip to main content
Glama

Search Companies House

company_search
Read-onlyIdempotent

Search Companies House by name or keyword to retrieve company details including status, SIC codes, incorporation date, and registered address. Paginated results.

Instructions

Search the Companies House register by company name or keyword.

Returns a paginated list of matching companies with name, number, status, SIC codes, incorporation date, and registered address. Use company_profile for the full record once you have the company number. Re-call with start_index=start_index+items_per_page to fetch the next page.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYesCompany name or keyword to search for
company_statusNoFilter by company status (e.g. 'active', 'dissolved'). Omit to search all.
company_typeNoFilter by company type (e.g. 'ltd', 'llp'). Omit to search all.
items_per_pageNoNumber of results to return (max 100). Default 20.
start_indexNoPagination offset. Default 0.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYesThe query string that was searched.
total_resultsYesTotal matching companies in Companies House (server-side).
start_indexYesNumber of results skipped before this page (upstream start_index).
items_per_pageYesPage size requested from the API for this call.
returnedYesNumber of items actually returned on this page.
has_moreYesTrue if more results exist beyond this page. Re-call with start_index=start_index+items_per_page to fetch the next page.
itemsNoMatching companies. Use the `company_number` field to call company_profile, company_officers, or company_psc for full detail.
Behavior5/5

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

Annotations already declare readOnlyHint, destructiveHint, idempotentHint. Description adds that results are paginated and lists returned fields. No contradiction.

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

Conciseness5/5

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

Three sentences: purpose, output summary, usage guidance. No wasted words, front-loaded.

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

Completeness5/5

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

With output schema present, description needn't detail return types. Provides pagination, alternative tool, and result summary - fully adequate for a search tool.

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

Parameters4/5

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

Schema coverage is 100% so baseline is 3. Description adds value by summarizing output fields (name, number, status, SIC codes, etc.) beyond schema descriptions.

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

Purpose5/5

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

Clearly states 'Search the Companies House register' with specific verb and resource. Distinguishes from sibling 'company_profile' which is for full records.

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

Usage Guidelines5/5

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

Explicitly tells when to use 'company_profile' instead and provides pagination instructions: 'Re-call with start_index=start_index+items_per_page to fetch the next page.'

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/paulieb89/uk-due-diligence-mcp'

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