Skip to main content
Glama

UK KYB & Credit Risk MCP Server

check_company_check_company__company_number__get

Check Company

Evaluates the financial health, statutory filing compliance, beneficial ownership (PSC), governance stability, and credit risk of a single UK registered company.

Responses:

200: Successful Response (Success Response) Content-Type: application/json

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_number": "<company_number>"
    },
    "name": "check_company_check_company__company_number__get"
  }
}

Input Schema

NameRequiredDescriptionDefault
company_numberYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.7/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden. It discloses what dimensions are evaluated, which is useful, but says nothing about auth requirements, rate limits, error behavior for unknown company numbers, latency of a multi-source check, or whether results are cached or real-time.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

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

The opening purpose and the list of evaluated dimensions are front-loaded and earn their place. However, the 'Responses: 200 Successful Response / Content-Type: application/json' block is boilerplate scaffolding that conveys nothing an agent can act on.

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

Completeness3/5

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

With no annotations and no output schema, the description is the only source of truth. It does a fair job indicating the scope of the report (five evaluation areas), but gives no sense of the response structure or key fields, and leaves the parameter format entirely undocumented.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% for the single required parameter, so the description must compensate and it does not. It never states that company_number is a UK Companies House registration number, its expected format (typically 8 characters, possibly with a prefix), or whether it is case/format sensitive.

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 ('Check Company') and enumerates the concrete dimensions examined: financial health, statutory filing compliance, beneficial ownership (PSC), governance stability, and credit risk. It also scopes the target to 'a single UK registered company', which implicitly separates it from the batch sibling, though it never names that sibling.

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 or when-not-to-use guidance, no prerequisites (e.g., a valid Companies House number), and no routing to batch_check_uk_companies for multiple companies. The word 'single' provides only the faintest hint at an alternative.

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