Skip to main content
Glama

TrustCheck by RecoupIQ: UK Company Facts

UK company risk indicators

risk_assess
Read-onlyIdempotent

Returns a 0 to 100 forensic risk score, risk band, and source-backed governance, premises, licence-gap, solvency, and filing indicators for a UK company. Indicators only, not advice. Each answer states its record date and its source.

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": {
      "companyNumber": "<companyNumber>"
    },
    "name": "risk_assess"
  }
}

Input Schema

NameRequiredDescriptionDefault
companyNumberYesUK Companies House registration number, 8 uppercase alphanumeric characters.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already establish the safety profile (readOnly, idempotent, non-destructive, closed-world), so the bar is lower. The description adds genuinely useful behavior beyond them: every answer carries a record date and its source, which tells the agent results are provenance-stamped and point-in-time rather than live. It does not disclose scoring methodology, thresholds between bands, or coverage limits when data is missing.

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 shape, followed by the advice disclaimer and the provenance note. No filler or repetition.

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?

No output schema exists, yet the description sketches the return payload (score, band, indicator categories) and notes that each answer states record date and source, which covers what an agent needs to consume results. It stops short of explaining band thresholds or how to treat missing indicators, a minor gap for a single-parameter read tool.

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?

With a single parameter at 100% schema coverage, the schema already defines the 8-character uppercase alphanumeric Companies House format and the description adds nothing further about it. Baseline 3 applies since the schema does the semantic work.

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 with concrete outputs: a 0-100 forensic risk score, risk band, and named indicator families (governance, premises, licence-gap, solvency, filing) for a UK company. That output profile implicitly distinguishes it from siblings like cross_border_assess or company_status, but no sibling is named, so the distinction must be inferred.

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 when-to-use guidance, no prerequisites, and no routing to alternatives such as cross_border_assess for non-UK exposure or company_status for plain registry facts. The only boundary offered is the disclaimer 'Indicators only, not advice', which constrains interpretation but does not tell an agent when to pick this tool over its siblings.

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