Skip to main content
Glama

Registry Pages

UK company by company number

get_uk_company
Read-only

Companies House register data for one UK company: name, status, type, incorporation date, registered office, SIC codes, accounts and confirmation statement dates, previous names, and the page URL to cite.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "number": "<number>"
    },
    "name": "get_uk_company"
  }
}

Input Schema

NameRequiredDescriptionDefault
numberYesCompany number, for example 00445790 or SC123456

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds genuine context beyond that by specifying the returned field set and the citable page URL, which matters for a read tool with no output schema. It does not say what happens for an unknown or malformed company number, which keeps it from a 5.

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?

A single sentence front-loads the resource and scope, then lists the return fields compactly. No throat-clearing, no repetition of the tool name, nothing that could be cut.

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?

With a single required parameter, annotations covering safety, and no output schema, the description carries the return-value burden and does so by enumerating the fields. Only edge behavior (not-found or invalid number) is unaddressed, a minor gap for a lookup tool of this simplicity.

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 there is only one parameter, whose example formats (00445790, SC123456) are already in the schema. The description adds no further meaning such as jurisdiction prefixes or normalization rules, so the baseline 3 applies.

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 a specific resource (one UK company's Companies House register record) and enumerates exactly what comes back: name, status, type, incorporation date, registered office, SIC codes, accounts and confirmation statement dates, previous names, page URL. That clearly separates it from the plural search siblings, though no alternative is named explicitly.

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

Usage Guidelines3/5

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

Usage is implied rather than stated: 'for one UK company' signals a single-entity lookup best used when you already have a company number, versus the search_uk_companies style tools. There is no explicit when-to-use/when-not-to-use sentence or instruction to fall back to search when the number is unknown.

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