Skip to main content
Glama

Cybercentry B20 Token Verification

verify_quote_asset

Settle any token address against the issuer's published tokenized-stock list and read what it is a claim on — a quote asset, a basket, an ERC-4626 wrapper. Synchronous, no polling. 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_quote_asset"
  }
}

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

A3.7/5.0
Behavior4/5

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

With no annotations, the description does real work: it declares synchronous behavior with no polling, a $1 USDC cost, and a payment gate that blocks the call otherwise. It also characterizes the return as a claim classification (quote asset, basket, ERC-4626 wrapper). It stops short of describing failure behavior for addresses not on the published list.

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?

Two sentences, front-loaded with the core action and its scope, followed by operational facts (sync, cost, payment). No filler or restated title; the em-dash enumeration of claim types is functional, not decorative.

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?

Payment flow and synchronous behavior are covered, which are the highest-risk unknowns for this tool. However, with no output schema, the description should say more about what the response contains and what happens when an address is not on the issuer's list (error vs. an 'unverified' result). That negative-path gap leaves it only adequate.

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 chain, address, txHash, and paymentId are already documented in the schema. The description only reinforces the payment-reference requirement and does not add format or selection detail (e.g., why choose txHash over paymentId) beyond what the schema states. Baseline 3 applies.

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?

"Settle any token address against the issuer's published tokenized-stock list and read what it is a claim on" gives a specific verb and resource, and the tokenized-stock-list scope implicitly separates it from verify_b20_token. It never names a sibling explicitly, so differentiation is inferential rather than stated.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied (verify a token address against the issuer's list) and one prerequisite is stated clearly: a $1 USDC payment reference is required. There is no guidance on when to prefer verify_b20_token or get_verification_report instead, and no stated exclusions.

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.