Skip to main content
Glama

TrustCheck by RecoupIQ: UK Company Facts

UK company name match

entity_resolve
Read-onlyIdempotent

Returns ranked UK Companies House registration numbers for a fuzzy company name with confidence scores and company status flags. Pass an optional UK postcode to improve match precision. Indicators only, not advice.

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

Input Schema

NameRequiredDescriptionDefault
limitNo
queryYesCompany name as shown on an invoice, contract, or order.
postcodeHintNoOptional UK postcode hint to narrow candidate matches.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, so safety is covered; the description goes further by disclosing what is returned (ranked registration numbers, confidence scores, status flags), that matching is fuzzy, and that a postcode hint improves precision. It also adds a useful limits statement ('Indicators only, not advice'). Gaps: no mention of what happens on zero matches, how confidence scores should be interpreted, or the 25-result cap.

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 return value, then the optional precision control, then the liability caveat. No filler, no restatement of the tool name, and each sentence adds something.

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 three parameters and no output schema, the description carries the burden of explaining return values and does so competently (ranked registration numbers, confidence scores, status flags). Relative to a read-only lookup tool this is nearly complete; only edge-case behavior (no matches, limit interaction, score interpretation) is unaddressed.

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 67%; query and postcodeHint are documented in the schema, and the description largely restates them ('fuzzy company name', 'optional UK postcode to improve match precision') rather than adding new meaning such as expected format or how strong the precision improvement is. The limit parameter (1-25) is never mentioned in either the description or via a schema description, leaving its effect on ranking unexplained.

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: returns ranked UK Companies House registration numbers from a fuzzy company name, with confidence scores and status flags. An agent can tell this is a name-to-number resolver rather than a status lookup, though it never names sibling tools like company_status or check_company_seal, and the mention of 'company status flags' slightly blurs the line with company_status.

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 explicit when-to-use guidance, no exclusions, and no named alternatives despite six siblings including company_status and risk_assess. The only hints are implicit: 'fuzzy company name' (shown in the schema as coming from an invoice, contract, or order) and 'Pass an optional UK postcode to improve match precision'. The closing line 'Indicators only, not advice' is a disclaimer, not usage routing.

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