RunOnProof

verify_uk_company_status

Read-onlyIdempotent

Paid x402 UK tool for gb.company.legal_status.verify.v1 (AVAILABLE). Claims are limited to the named official sources.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`company_number`	Yes	Companies House company number, including any two-letter prefix when applicable.
`idempotency_key`	Yes	Caller-generated key. Send the identical value in the Idempotency-Key header.

Output Schema

TableJSON Schema

Name	Required	Description
`policy`	Yes
`result`	Yes	Offer-specific facts and machine-action inputs; interpret with decision, coverage and limitations.
`payment`	Yes
`coverage`	Yes	Country, population and explicit coverage limitations.
`decision`	Yes
`evidence`	Yes	Source-scoped evidence references; absence is never a clean finding.
`replayed`	No
`conditions`	Yes
`request_id`	Yes
`delivery_id`	No
`limitations`	Yes
`valid_as_of`	Yes
`valid_until`	Yes
`execution_id`	No
`reason_codes`	Yes
`authorization`	Yes
`source_health`	Yes
`machine_action`	Yes
`schema_version`	Yes
`economic_activity`	Yes
`product_or_solution`	Yes
`required_information`	Yes

TDQS

C2.9/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is clear. The description adds that it is 'Paid' and that 'Claims are limited to the named official sources', which is useful behavioral context about scope and cost. However, it does not disclose failure modes, output shape, or latency.

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 description is very brief—two short sentences. It front-loads the tool's paid nature and service identifier. The phrase 'x402' and '(AVAILABLE)' are somewhat cryptic, but the overall size is minimal and every sentence adds some information.

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?

Given the tool has an output schema, the description need not explain return values. It covers cost and source limitation, but in the context of many sibling verification tools, it lacks usage context and clear differentiation. It is minimally complete but not rich.

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 description coverage is 100%, and both parameters (company_number, idempotency_key) have detailed descriptions. The tool description adds no extra parameter semantics, so the schema carries the burden. Baseline of 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description references 'gb.company.legal_status.verify.v1' and the tool name 'verify_uk_company_status', which together imply verifying UK company legal status. However, it never directly states 'verifies UK company status' in plain language, relying on the service identifier. It does distinguish somewhat from siblings like verify_uk_business_licence or verify_uk_tax_registration, but the wording is cryptic.

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?

No guidance is provided on when to use this tool versus the many sibling verification tools. The description mentions 'Paid' and 'Claims are limited to the named official sources' but does not explain prerequisites, alternatives, or contexts where this should be preferred.

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

All RunOnProof tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

C2.4/5.0

Disambiguation2/5

Multiple tools appear to address the same action with only country or payment-model differences, such as company_check/run_uk_company_check, approve_supplier/approve_uk_supplier, authorize_payment/run_uk_payment_authorization, and screen_restricted_party/screen_restricted_business_party. Even with descriptions, an agent will struggle to pick the intended tool reliably.

Naming Consistency2/5

Naming mixes bare global verbs (company_check, approve_supplier, authorize_payment) with UK-prefixed variants (run_uk_company_check, approve_uk_supplier, authorize_uk_business_payment), plus free-form names like counterfactual, preflight, quote, and capabilities. There is no single consistent verb_noun or country-modifier convention across the set.

Tool Count2/5

46 tools is far beyond the typical well-scoped MCP surface, and the set carries heavy duplication through global/UK/free/paid variants. While the domain may justify multiple country-specific operations, the tool count itself will overwhelm agents and make selection harder.

Completeness4/5

The server covers the main compliance lifecycle well: discovery (capabilities, preflight, quote, resolve_agent_intent), verification, supplier approval, payment authorization, invoice matching, passport issuance/refresh, and verification receipts. Minor gaps exist around explicit cancellation/revocation or list/search operations, but core workflows have no major dead ends.

Resources

Need Help?