Skip to main content
Glama

UK KYB & Credit Risk MCP Server

batch_check_uk_companies

Check Companies Batch

Batch-evaluates up to 10 UK companies in a single call for AI agents verifying multiple suppliers.

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_numbers": "<company_numbers>"
    },
    "name": "batch_check_uk_companies"
  }
}

Input Schema

NameRequiredDescriptionDefault
company_numbersYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.8/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden and mostly fails: it does not say what happens if more than 10 company numbers are passed (error vs truncation), whether failures are partial per-company or all-or-nothing, whether authentication is required, or anything about the response body beyond a bare 200 status line.

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 core sentence is tight and front-loaded, but the '### Responses: **200**: Successful Response (Success Response) Content-Type: application/json' block is auto-generated boilerplate that conveys no information an agent can act on.

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

Completeness2/5

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

There is no output schema, so the description is the only source of return-value information, and it provides none beyond an HTTP status. For a batch tool, the agent also needs to know the over-limit behavior and the failure model, both absent.

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?

The single parameter company_numbers has 0% schema description coverage, so the description must supply the identifier semantics. It only says 'UK companies' and never specifies the expected format (e.g. 8-character Companies House numbers), whether strings or ints are accepted, or whether duplicates/ordering matter.

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: 'Batch-evaluates up to 10 UK companies in a single call.' The batch scope and the 10-item cap distinguish it from the single-company sibling check_company_check_company__company_number__get, though the description never names that sibling explicitly.

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?

'For AI agents verifying multiple suppliers' implies the multi-record scenario is the trigger, but no explicit when-to-use/when-not rule is given, and the single-company alternative is never referenced. The agent must infer the routing decision from the batch wording alone.

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