Skip to main content
Glama

Cybercentry B20 Token Verification

verify_b20_token

Start a Cybercentry B20 token verification: can this token actually be sold? Checks pool-hook honeypots, whitelisted exits, freeze-and-seize, live pauses, fakes and issuer controls. Returns a jobId — poll it with get_verification_report. Costs $1 USDC, so a payment reference is required.

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

Input Schema

NameRequiredDescriptionDefault
chainNo'base' (mainnet, default) or 'base-sepolia' (testnet).
txHashNoProof the scan was paid for. Supply ONE of `txHash` (a Base transaction hash for a $1 USDC transfer to the treasury) or `paymentId` (a Base Pay payment id). Each is single-use. Without one the call returns 'Payment required'.
addressYesThe token contract address to verify, as 0x followed by 40 hex characters.
paymentIdNoProof the scan was paid for. Supply ONE of `txHash` (a Base transaction hash for a $1 USDC transfer to the treasury) or `paymentId` (a Base Pay payment id). Each is single-use. Without one the call returns 'Payment required'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses the async jobId contract, the $1 USDC cost, the payment gate and the resulting error string, plus what categories of risk the scan covers. It omits how long the job runs, whether payment is consumed on failure, and whether the address is validated up front.

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?

Three tight sentences: what it does, what the scan covers, what it returns and what to do next, then the cost/payment constraint. Front-loaded and every sentence carries new information with no filler.

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?

Covers the essentials an agent needs: initiating call, async handoff to get_verification_report, and the payment prerequisite. Since there is no output schema, the description could say more about what the eventual report contains or how fast the job completes, but nothing critical to invoking it correctly is missing.

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% and the schema already explains chain, address, txHash and paymentId in detail, including the single-use and 'Payment required' behavior. The description only reinforces the payment premise ('a payment reference is required') without adding format or selection guidance beyond the schema, so the baseline 3 applies.

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?

Names a specific verb and resource ('Start a Cybercentry B20 token verification') and frames the outcome as a concrete question ('can this token actually be sold?'). The checklist of honeypots, exits, freezes, pauses, fakes and issuer controls makes the scope unmistakable and separates it from get_verification_report, which it explicitly names as the polling step.

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 clear operational context: this is the starting call, results come from get_verification_report, and a payment reference is required or the call fails with 'Payment required'. It does not distinguish from verify_quote_asset, and there is no explicit 'do not use this for X' exclusion, so it falls short of a 5.

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.