Skip to main content
Glama

kyb_check_uk

Run a one-call UK company KYB check to retrieve Companies House profile, officers, filing status, insolvency flags, and sanctions screening, then get a pass/review/fail verdict.

Instructions

One-call KYB for a UK company (company number or name): Companies House profile, officers and filing status, insolvency/liquidation flags, plus sanctions screening (US CSL/OFAC, EU, FR, UK) of the registered name, with a pass/review/fail verdict and flags. Costs 0.01 USDC on Base per successful call (x402). Without a payment key this tool returns the 402 challenge.

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

Input Schema

NameRequiredDescriptionDefault
nameNoName (alternative; best match is checked)
company_numberNo8-char company number

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.0

TDQS

A4.4/5.0
Behavior5/5

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

With no annotations, the description carries the full burden and does so: it discloses the 0.01 USDC cost on Base via x402, that billing is per successful call, and precisely what happens without a payment key (a 402 challenge rather than an error). It also discloses the return shape — a pass/review/fail verdict plus flags — which is essential given 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose and evidence bundle are front-loaded, and the payment caveat follows immediately where it is most needed. The opening sentence is dense with stacked clauses (officers, filing status, insolvency, four sanctions lists), which is efficient but slightly heavy to parse in one pass.

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 two-parameter tool with no annotations and no output schema, everything an agent needs is present: what is checked, what the verdict vocabulary is, what it costs, and how failure to pay manifests. Nothing material is left for the agent to guess.

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%, with both parameters already documented, so the baseline is 3. The description confirms either a company number or a name is accepted but adds no format, precedence, or ambiguity-resolution detail beyond the schema's own note that the best match is checked.

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 and resource ('One-call KYB for a UK company') and enumerates the exact evidence bundle returned: Companies House profile, officers, filing status, insolvency/liquidation flags, and multi-jurisdiction sanctions screening. The UK jurisdiction qualifier cleanly separates it from the kyb_check_eu and kyb_check_fr 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?

Usage context is clear — UK incorporation checks, accepting either a company number or a name — and the payment precondition is stated outright ('Without a payment key this tool returns the 402 challenge'). It stops short of explicit when-not guidance or naming kyb_check_eu/kyb_check_fr as the alternatives for non-UK entities, leaving that routing to inference from the jurisdiction tag.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.