Skip to main content
Glama

uk_company

Search or look up UK companies via Companies House by name or number to retrieve profiles, officer counts, filing status, and insolvency or charges flags.

Instructions

UK company register (official Companies House API): search by name, or lookup by company number with profile (status, type, incorporation/dissolution, SIC codes, registered office, previous names), officer counts (active/resigned) and filing status (accounts and confirmation statement due/overdue), insolvency, liquidation and charges flags. Costs 0.002 USDC on Base per successful call (x402). Without a payment key this tool returns the 402 challenge.

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
maxNo1-20
nameNoName search (alternative)
company_numberNo8-char company number

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.0

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and largely meets it: it discloses a per-call price (0.002 USDC on Base), the x402 payment protocol, that only successful calls are charged, and that calls without a payment key return a 402 challenge. That payment/failure behavior is exactly the kind of context annotations would otherwise provide. It does not cover rate limits, paging behavior, or what happens when neither identifier is supplied.

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?

The core capability and the two modes are front-loaded in the first sentence, with payment terms following. The long parenthetical field list is dense but earns its place given there is no output schema; the sentence is somewhat run-on but not padded.

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 three-parameter tool with no output schema and no annotations, the description supplies the returned fields, the cost model, and the auth failure mode. The one meaningful gap is that zero parameters are required while name and company_number are alternatives — the agent is not told what happens if both or neither are provided, nor what the result list looks like for a name search.

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%, so the schema already documents all three parameters, and the description only restates the name-vs-number split without adding format rules. The `max` parameter (1-20) is never mentioned in the description at all, so nothing beyond the schema is contributed.

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 names a specific resource (UK company register, official Companies House API) and two explicit operations: name search and lookup by company number. It also enumerates the payload contents (status, type, incorporation/dissolution, SIC codes, registered office, previous names, officer counts, filing status, insolvency/liquidation/charges flags), so an agent can tell this is a UK-specific company data tool distinct from the other country registers among its siblings.

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 clearly splits the two invocation modes — search by name versus lookup by company number — which is real when-to-use guidance tied to the parameters. It stops short of naming an alternative sibling (e.g. kyb_check_uk) or stating exclusions, so it is clear context without explicit routing.

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