Skip to main content
Glama

OnchainDiligence

by com.onchaindiligence

verify_uk_company

Read-only

UK company verification and KYB (know-your-business) lookup via the official Companies House register. Given a UK company registration number, returns legal status (active / dissolved), company type, incorporation date, registered office address, and the people with significant control (PSC / beneficial owners). Use for KYB onboarding, supplier and counterparty due diligence, and confirming a UK business is real, active, and who controls it. Authoritative UK government open data.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
companyNumberYesUK Companies House registration number to verify, e.g. 00000006

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true. The description adds value by noting it is 'authoritative UK government open data' and specifying the returned data types (legal status, PSC, etc.). No contradiction with annotations, and the description enhances understanding of the tool's behavior.

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 five sentences, efficiently covering purpose, returned data, use cases, and authority. It is well-structured and front-loaded. Minor room for further conciseness, but overall very good.

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?

Given the tool's simplicity (1 parameter, no output schema), the description adequately lists the types of data returned (legal status, company type, incorporation date, address, PSC). It does not cover error handling or output format, but for a read-only lookup, it provides sufficient context.

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%, with the parameter companyNumber fully described. The description restates 'given a UK company registration number' but does not add significant new meaning beyond the schema's description and example. Baseline 3 is appropriate.

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?

The description clearly states it performs UK company verification and KYB lookup via Companies House, specifying the exact returned fields (legal status, type, incorporation date, address, PSC). It distinguishes itself from the sibling verify_us_company by being UK-specific and provides a distinct set of data.

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?

The description explicitly lists use cases: 'KYB onboarding, supplier and counterparty due diligence, and confirming a UK business is real, active, and who controls it.' It does not explicitly state when not to use, nor does it compare to siblings like screen_name or diligence, but the context is clear enough for an agent.

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

All OnchainDiligence toolsInspect
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

A4.3/5.0
Disambiguation4/5

Each tool has a distinct purpose, but 'diligence' overlaps with the combination of 'screen_wallet' and 'verify_uk_company', which could cause confusion about when to use the combined vs. individual tools. However, the descriptions clearly delineate that 'diligence' runs both checks in parallel with an additional disclaimer, so the ambiguity is limited.

Naming Consistency4/5

Four of five tools follow a clear verb_noun pattern (screen_name, screen_wallet, verify_uk_company, verify_us_company), but 'diligence' is a bare noun that doesn't fit the convention. This minor deviation is still readable and predictable overall.

Tool Count5/5

With 5 tools, the set is well-scoped for a compliance/due diligence server. Each tool covers a distinct aspect (name screening, wallet screening, UK company verification, US company verification, and a combined diligence option) without unnecessary bloat or trivial additions.

Completeness5/5

The tool surface covers the core due diligence workflows: sanctions screening for both names and wallets, company verification for both UK and US entities, and a combined diligence call that ties together the on-chain and off-chain checks. There are no obvious dead ends or missing critical operations within the stated domain.

Resources