Skip to main content
Glama

Counterparty Pre-Wire Live Proof Dossier

counterparty_live_dossier
Read-onlyIdempotent

Unified pre-wire proof combining IBAN/BIC syntax, live registry lookup, retained exact-match sanctions snapshot, legal-name token match, country consistency, and signed receipt.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "lei": "506700GE1G29325QX363",
      "expected_name": "Global Legal Entity Identifier Foundation"
    },
    "name": "counterparty_live_dossier"
  }
}

Input Schema

NameRequiredDescriptionDefault
bicNoOptional beneficiary SWIFT BIC for ISO 9362 check and country alignment
leiNo20-character LEI for live GLEIF observation
ibanNoOptional beneficiary IBAN for ISO 7064 MOD-97 check and country alignment
uk_crnNoUK company number for live corporate observation
no_orgnrNo9-digit Norwegian organization number for live Brreg observation
vat_numberNoEU VAT number for live VIES observation (requires vat_purpose='eu_intra_community_transaction')
evm_addressNoOptional counterparty 0x wallet for retained exact-match sanctions snapshot screen
vat_purposeNoRequired when vat_number is supplied
expected_nameNoOptional expected counterparty legal name to compare against live registry name
vat_country_codeNoOptional 2-letter EU/XI VAT prefix

Output Schema

NameRequiredDescriptionDefault
validNo
dossier_summaryNo
name_comparisonNo
sanctions_exact_screeningNo
live_registry_observationsNo
existence_verified_at_registryNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already cover readOnly, idempotent, and open-world behavior, so the description's marginal burden is lower. It does add genuinely useful nuance: the sanctions screen is described as a "retained exact-match snapshot" rather than a live query, contrasting with the explicitly "live" registry lookups, and it discloses that a signed receipt is produced. It says nothing about latency, cost, failure/partial-result behavior when a registry is unreachable, or what the signature attests to.

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?

A single dense sentence with no filler and the deliverable front-loaded ahead of the component list. It is readable, though the six-item comma chain is run-on and could have been split to separate inputs from outputs (checks versus signed receipt).

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?

With ten parameters, zero required, an output schema, and annotations, the definition is close to sufficient, but the all-optional schema raises an unanswered question: is at least one identifier (IBAN, LEI, CRN, VAT, wallet) required for a meaningful dossier, and what happens with none supplied? The description also never states what the signed receipt contains, though the output schema presumably covers return shape.

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%, so the schema already documents all ten inputs, and the description's paraphrase (IBAN/BIC syntax, live registry lookup, country consistency) largely restates it. It adds one meaningful clarification by calling the name comparison a "legal-name token match," hinting that expected_name is matched by tokens rather than exact equality. It does not clarify the interaction between vat_number and vat_purpose or vat_country_code, nor how multiple identifiers are combined.

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?

The description names a concrete deliverable (a pre-wire proof dossier) and enumerates the specific checks it bundles: IBAN/BIC syntax, live registry lookup, sanctions snapshot, name token match, country consistency, signed receipt. An agent can distinguish it from point-check siblings like iban_check or lei_live_lookup because it is explicitly the unified bundle. It stops short of a clean verb-plus-resource statement, reading more as a feature list than a definition.

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?

The phrase "pre-wire proof" weakly implies the moment of use (prior to releasing a payment), but there is no explicit when-to-use, when-not-to-use, or routing to alternatives. Nothing tells the agent whether to call this instead of the individual lookups (lei_live_lookup, vat_vies_live_lookup, iban_check) or in addition to them, nor what to do when only one identifier is available.

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.