Skip to main content
Glama

Registry Pages

Search UK companies by name

search_uk_companies
Read-only

Find UK companies still on the Companies House register by name. Returns at most 10 matches with company number, postcode, status and page URL. Use get_uk_company for details.

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": {
      "query": "<query>"
    },
    "name": "search_uk_companies"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesCompany name, for example "tesco"

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/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 genuinely new behavioral facts beyond that: a hard cap of 10 results and the exact fields returned (company number, postcode, status, page URL), which matters since there is no output schema. It does not discuss match ranking or what an empty result looks like.

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?

Three short sentences, front-loaded with the action and scope, then the result shape, then the alternative tool. Nothing is redundant or padded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a one-parameter read-only search tool with full schema coverage and annotations, the description supplies everything an agent needs: what it searches, the result ceiling, the returned fields, and where to go for more detail.

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?

Single required 'query' parameter with 100% schema description coverage including an example, so the schema carries the semantics. The description only restates that lookup is by name; it adds no matching rules (partial vs exact, case sensitivity) beyond the schema.

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?

States a specific verb (find/search) and resource (UK companies) plus a meaningful scope constraint: only companies still on the Companies House register. That scope and the name-based lookup distinguish it cleanly from get_uk_company and from the French/Norwegian search 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?

Explicitly routes the agent to get_uk_company when full details are needed, and the 'still on the register' filter implicitly excludes dissolved entities. No explicit statement about what to do when zero matches are returned or about the other country-specific search tools, but the core when-to-use signal is present.

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