Skip to main content
Glama

United Kingdom company

run_uk_companies
Read-onlyIdempotent

Get one company from the United Kingdom registry (Companies House) by registration number or registry URL: name, status, registration date, address and legal form. Flat 30 points per successful run.

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": {
      "company": "<company>"
    },
    "name": "run_uk_companies"
  }
}

Input Schema

NameRequiredDescriptionDefault
companyYesRegistration number or registry URL. e.g. 00445790

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, open-world, and non-destructive behavior. The description adds useful behavioral context by listing returned fields and disclosing the cost model: "Flat 30 points per successful run." It does not discuss not-found or error behavior, but the safety profile is well covered.

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 tight sentences with the core action and lookup key front-loaded. The returned-field list and pricing note are relevant and do not distract from the main instruction.

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 one-parameter lookup tool with no output schema, the description identifies the source registry, accepted identifier forms, and the main returned fields. It is nearly complete; only failure behavior for invalid or not-found identifiers is unstated.

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%, and the schema already documents the sole parameter as "Registration number or registry URL" with example "00445790." The description repeats that accepted input but adds no format constraints or syntax detail beyond the schema, so 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 states a specific verb and resource: "Get one company from the United Kingdom registry (Companies House)" and specifies the lookup key as registration number or registry URL. It also distinguishes this from a search/list tool by emphasizing retrieval of one company, and lists the returned fields.

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?

Usage is clear: call this when you already have a company registration number or registry URL and need that single company's record. However, it does not explicitly name run_uk_companies_search as the alternative for name-based discovery, so routing guidance is implied rather than explicit.

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