Skip to main content
Glama

Lookup Company

lookup_company
Read-onlyIdempotent

Look up a UK company on Companies House: search by name to find candidates, or fetch one by its number for the public record, its directors and its filing dates. Needs no account. Without an account it is UK only.

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": "lookup_company"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryNoCompany name to search for (returns up to ~10 candidates with number, status, and address). Use when you have a name but not a number.
companyNoWhich company to read, by name or id, when the account has more than one (see list_companies). Leave it out to use the only company, or the default.
company_numberNoExact company number to fetch the full record + directors + deadlines. Use once you know the number (e.g. after the user confirms a search candidate).

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 cover the safety profile (readOnly, idempotent, non-destructive, open-world), so credit goes to what the description adds: it discloses that no account is needed and that unauthenticated use is UK-only. It also lists the payload contents (record, directors, filing dates), which matters because there is no output schema.

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 compact sentences, front-loaded with the resource and source system, followed by the account/coverage caveat. Every clause carries information and nothing is redundant.

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, no-required-argument lookup with no output schema, the description covers what the tool returns, the two invocation modes and the authentication/geography constraint. Only the multi-company scoping parameter is left entirely to the schema, which is a minor gap.

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 the schema already documents query, company and company_number in detail. The description only restates the name-vs-number split and says nothing about the account-scoping 'company' parameter, so it adds little beyond the schema; 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 verb and resource ('Look up a UK company on Companies House') and explicitly splits the tool into two modes: name search returning candidates, and number lookup returning the public record, directors and filing dates. It does not differentiate from the similarly named sibling check_company, so it stops 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 Guidelines3/5

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

Usage is implied through the two modes: search when you have a name, fetch when you have a number. There are no explicit exclusions or pointers to alternatives such as check_company or read_company_wiki, so an agent must infer which sibling to pick.

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.