Skip to main content
Glama

OnchainDiligence

by com.onchaindiligence
OverviewDiscussionsAdmin

diligence

Read-only

Combined counterparty due diligence in one call: runs sanctions screening on a crypto wallet (Chainalysis oracle — OFAC SDN, EU, UN) AND a UK Companies House KYB lookup (status, type, PSC / beneficial owners) in parallel. Built for compliance agents vetting a counterparty that has both an on-chain wallet and a UK company. Returns both independent results, plus an explicit disclaimer that no verified link between the wallet and the company is established by the data.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
walletYesEVM wallet address (0x + 40 hex) to sanctions-screen
companyYesUK Companies House registration number to verify

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / company / description
      Previous value: -"UK company registration number"New value: +"UK Companies House registration number to verify"
    • changedInput schema / properties / wallet / description
      Previous value: -"EVM wallet address (0x + 40 hex)"New value: +"EVM wallet address (0x + 40 hex) to sanctions-screen"
  2. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Discloses parallel execution, independent results, and a disclaimer about no verified link. Adds value beyond readOnly and openWorld annotations.

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?

Single concise paragraph, no wasted words, effectively front-loaded with the main function.

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?

Adequately describes the combined function and use case, but lacks details on result structure since no output schema exists.

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 coverage is 100% with clear descriptions. Description adds no additional detail beyond what's in the schema.

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?

Description clearly states it combines sanctions screening on a crypto wallet and UK Companies House KYB lookup. It distinguishes from sibling tools like screen_wallet and verify_uk_company by offering a combined call.

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?

Explicitly states it's built for compliance agents vetting a counterparty with both an on-chain wallet and a UK company. Implies not to use if only one check is needed, but lacks explicit exclusion.

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
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources