Skip to main content
Glama

Companies House

by io.github.pipeworx-io

Get Company

get_company
Read-onlyIdempotent

Fetch a single UK company profile by company number. Returns registered name, status, type, SIC codes, registered office, accounts/confirmation-statement due dates, and links to officers/filings/charges/PSCs.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
company_numberYesUK company number (e.g., "00006245")

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesRegistered company name
typeYesCompany type (private limited, public limited, etc.)
ch_urlNoLink to company profile on Companies House website
statusYesCompany status (active, dissolved, etc.)
sic_codesYesStandard Industrial Classification codes
dissolved_onNoDissolution date (ISO format) if applicable
jurisdictionNoCompany jurisdiction (England and Wales, Scotland, etc.)
status_detailNoAdditional status details
company_numberYesUK company number
incorporated_onYesIncorporation date (ISO format)
accounts_next_dueNoNext accounts filing due date (ISO format)
registered_officeNoRegistered office address details
accounts_next_made_up_toNoNext accounts period end date (ISO format)
last_accounts_made_up_toNoLast filed accounts period end date (ISO format)
confirmation_statement_next_dueNoNext confirmation statement due date (ISO format)

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive. Description adds value by detailing exact return fields (status, type, SIC codes, etc.) and links. Could mention error handling for missing company, but overall good.

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?

Two sentences: first states action, second lists returns. No fluff, efficient, and front-loaded with the key purpose.

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

Completeness4/5

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

Given output schema exists and annotations cover safety, description is thorough for a simple read tool. Lists all major return fields. Could mention pagination or rate limits, but not critical.

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 a good description of the parameter. Description reinforces it's a UK company number but adds no new syntax or format details. Baseline 3 is appropriate.

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?

The description clearly states the verb 'fetch' and the resource 'UK company profile', specifying the input as company number. It lists returned data, distinguishing it from sibling tools like search_companies (search) and get_filings (filings only).

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

Usage Guidelines4/5

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

Implied that this tool is for fetching a specific company by number, versus searching. No explicit when-not-to-use or alternatives mentioned, but the context is clear enough.

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

All Companies House toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.6/5.0
Disambiguation2/5

Several tools have overlapping jobs: ask_pipeworx_beta is currently identical to ask_pipeworx, ask_pipeworx_grounded is the same router with stricter extraction, and discover_tools/suggest_questions both serve discovery. Company-facing tools also overlap (entity_profile vs recent_changes vs compare_entities), so an agent could easily route a query to the wrong tool despite detailed descriptions.

Naming Consistency3/5

Names are mostly snake_case and grouped prefixes like get_*, ask_pipeworx*, and polymarket_* are readable. However, conventions are mixed across the set: some are verb_noun (search_companies), some are noun phrases (entity_profile, deep_research, recent_changes), and the Companies House family sits awkwardly beside unrelated Pipeworx and prediction-market families.

Tool Count1/5

With 36 tools, the server is already heavy, but only five tools actually serve the named Companies House domain. The other 31 belong to Pipeworx querying, memory, subscriptions, and Polymarket trading, which is a severe mismatch between the server's stated purpose and its actual surface.

Completeness3/5

For UK company data, the core surface is mostly covered: search, company profile, filings, officers, and PSCs. However, charges and official document retrieval are missing even though get_company links to them, and the unrelated tools do nothing to complete the Companies House domain.

Resources