Skip to main content
Glama

Tolca: business verification (KYB)

verify-business

verify_business
Read-onlyIdempotent

KYB company verification and business registry verification before paying, onboarding or contracting a company (vendor due diligence). One call checks US, UK, EU and Canadian sanctions (CSL incl. OFAC SDN), company registries (UK Companies House, Canada federal), legal entity status (GLEIF) and contractor licences (Quebec, Washington, Oregon). Returns allow / review / block, 0-100 risk score, dated sources and an Ed25519-signed receipt. Input: name, optional country, region. Costs $0.05 USDC per call (x402 v2, Base or Solana). Send the HTTP header PAYMENT-SIGNATURE with your x402 payment, or call POST https://tolca.tonbot.ca/v1/verify-business with an x402 client.

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

Input Schema

NameRequiredDescriptionDefault
nameYesBusiness legal or trade name
regionNoState/province code: WA, OR or QC enables contractor-licence checks
countryNoISO 3166 alpha-2 country code, e.g. US, CA, GB

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior5/5

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

Annotations cover the safety profile (readOnly, idempotent, non-destructive, openWorld), but the description adds materially: the allow/review/block verdict, a 0-100 risk score, dated sources, an Ed25519-signed receipt, and — critically — a $0.05 USDC per-call cost with the required PAYMENT-SIGNATURE x402 header and fallback endpoint. Payment/auth preconditions are exactly the kind of context annotations cannot carry.

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?

Dense but front-loaded: what it verifies comes first, then return values, then inputs, then payment mechanics last. Every sentence carries information, though the single unbroken paragraph and the trailing endpoint URL make it slightly harder to scan than a bulleted breakdown would be.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema exists, and the description compensates fully by describing the verdict, score, sources, and signed receipt. Combined with cost and payment mechanics, an agent has everything needed to decide, invoke, and interpret the result without further lookups.

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?

The description only restates the input shape ('Input: name, optional country, region'), which the schema already documents at 100% coverage, including the region-to-licence-check linkage. It adds the useful note that country and region are optional, but nothing about format or precedence beyond 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?

States a specific verb+resource (KYB company verification / business registry verification) and enumerates exactly what one call covers: CSL/OFAC sanctions, UK Companies House and Canada federal registries, GLEIF entity status, and Quebec/Washington/Oregon contractor licences. That enumeration cleanly distinguishes it from siblings like sanctions_check, qc_licence, and company_enrich.

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?

Gives explicit triggering context — 'before paying, onboarding or contracting a company (vendor due diligence)' — which tells the agent when to reach for it. It stops short of naming alternatives (e.g. 'use sanctions_check if you only need screening'), so there is no explicit when-not guidance, but the usage context is unambiguous.

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.