Skip to main content
Glama

Live UK Corporate Existence & ISO 20022 Office Lookup

uk_company_live_lookup
Read-onlyIdempotent

Live UK corporate lookup returning company status, registered office structured into ISO 20022 XML, PO Box check, SHA-256 payload digest, and signed receipt.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

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

Input Schema

NameRequiredDescriptionDefault
company_numberYesUK Companies House registration number (e.g. 14043409 or SC123456)

Output Schema

NameRequiredDescriptionDefault
validNo
entityNo
statusNo
provenanceNo
registered_officeNo
existence_verified_at_registryNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint, so the safety profile is covered; the description adds real behavioral value by disclosing that the response includes ISO 20022 PstlAdr XML, a PO Box check, a SHA-256 payload digest and a signed receipt. It stops short of saying what happens on a non-existent company or whether lookups are rate-limited or billed.

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?

One front-loaded sentence with no filler; every clause names a distinct output artifact. The comma-spliced list of return fields is dense but does not waste words.

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?

An output schema exists, so return values need not be explained in prose, yet the description still summarizes the notable artifacts. For a one-parameter read-only lookup, the main remaining gap is failure-mode behavior when the company number is invalid or unknown.

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% and the single parameter is fully documented in the schema (UK Companies House number with examples), so the baseline is 3. The description adds no additional meaning about the identifier's format or accepted variants.

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?

States a specific verb and resource ('Live UK corporate lookup returning company status...') and enumerates the concrete outputs, so an agent knows this is a Companies House existence/office check rather than an LEI or VAT check. It does not explicitly name the sibling lookups it differs from, so it falls short of a 5.

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?

There is no when-to-use or when-not-to-use guidance: nothing says whether to call this before counterparty_live_dossier, whether company_number_format should be run first, or what to do when the number is not found. Usage is only inferable from the name and parameter.

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.