Skip to main content
Glama

Look up a UK company: officers, PSC and filings

uk_company
Read-only

A UK company from Companies House, by number (00445790) or name (best match plus up to four alternatives): status, incorporation date, registered office, SIC codes, accounts and confirmation-statement due dates with overdue flags, current officers (max 20), persons with significant control (max 10) and the last 10 filings with links. Crown copyright, Open Government Licence v3.0. Related tools on this server, for a different need: uk_insolvency when you need to search UK company insolvency notices. Price: $0.003 per successful call, paid with x402 (USDC on Base, Solana and 10 more networks); failed calls are not charged.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "uk_company"
  }
}

Input Schema

NameRequiredDescriptionDefault
qNoAlternative to number: a company name (best match, up to 5 candidates)
numberNoCompanies House number, e.g. 00445790 or SC123456

Output Schema

NameRequiredDescriptionDefault
sourceNo
companyNo
filingsNo
licenseNo
personsNo
accountsNo
officersNo
checkedAtNo
matchedByNo
confirmationStatementNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "accounts": {},
      +    "checkedAt": {},
      +    "company": {},
      +    "confirmationStatement": {},
      +    "filings": {},
      +    "license": {},
      +    "matchedBy": {},
      +    "officers": {},
      +    "persons": {},
      +    "source": {}
      +  },
      +  "type": "object"
      +}
  2. Added

TDQS

A4.1/5.0
Behavior5/5

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

Beyond the readOnlyHint/openWorldHint annotations, the description discloses the billing model ($0.003 per successful call via x402/USDC, failed calls not charged), the licensing terms (Crown copyright, OGL v3.0), and the result caps (max 20 officers, max 10 PSC, last 10 filings). These are non-obvious operational facts an agent needs before calling.

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

Conciseness4/5

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

Content is front-loaded: lookup keys and returned data first, then sibling routing, then price/licence. Every sentence carries information, though the first sentence is very dense and mixing licensing and pricing into the same paragraph slightly dilutes scanability.

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?

For a read-only lookup with a full output schema and annotated safety profile, the description covers identifiers, scope, caps, cost, and a sibling alternative — enough to call correctly. It redundantly enumerates return fields already covered by the output schema, and gives no guidance on the mutual-exclusivity or precedence of q vs number.

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 description coverage is 100%, so both q and number are already documented, including example formats. The description's 'best match plus up to four alternatives' only lightly extends the schema's 'best match, up to 5 candidates', and adds no conflict/precedence rule for when both q and number are supplied. Baseline 3 is appropriate.

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 names the exact source (Companies House), the two lookup keys (number like 00445790, or name), and enumerates the returned payload (status, incorporation date, registered office, SIC codes, due dates with overdue flags, officers, PSC, filings). It explicitly differentiates itself from the sibling uk_insolvency. The only weakness is that the opening is a noun phrase rather than an explicit verb, but the intent is unmistakable.

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?

It states the two selection paths (number vs name, with name giving a best match plus up to four alternatives) and points to uk_insolvency for a different need. That is clear routing guidance. It lacks explicit when-not conditions, e.g. what to do when a name is ambiguous or how to disambiguate further.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources