Skip to main content
Glama

crypto_token_report

Read-only

Token report (on-chain) — On-chain facts and risk signals for an ERC-20 token on Base or Ethereum: name, symbol, decimals, total supply, USD price and market cap where indexed, contract code size, upgradeable-proxy detection, and owner status (active or renounced), rolled into a LOW / MEDIUM / HIGH / CRITICAL risk level with plain-English flags. Price: $0.02 USDC (Base, via x402).

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": "crypto_token_report"
  }
}

Input Schema

NameRequiredDescriptionDefault
chainNooptional: base (default) or ethereum
addressYestoken contract address (0x...)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / address / description
      Previous value: -"token contract address (0x…)"New value: +"token contract address (0x...)"
    • changedInput schema / properties / chain / description
      Previous value: -"base or ethereum (default base)"New value: +"optional: base (default) or ethereum"
  2. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint=true, destructiveHint=false, openWorldHint=true), so the description is not required to restate that. It adds genuinely new behavioral context: this is a paid call costing $0.02 USDC via x402 on Base, and some values are only present 'where indexed', warning the agent that fields can be absent. It does not cover failure modes (unknown address, non-ERC-20 contract) or latency/payment settlement details, which keeps it at 4 rather than 5.

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?

Front-loaded with a one-word scope marker ('Token report (on-chain)') followed by a dense but purposeful field enumeration, so the agent learns the payload quickly. The trailing 'Price: $0.02 USDC (Base, via x402)' is efficient but mildly ambiguous next to the earlier mention of 'USD price', which could be misread as the token's price rather than the call's cost.

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?

There is no output schema, so the description must carry the return-shape burden — and it does, listing every returned field and the LOW/MEDIUM/HIGH/CRITICAL risk scale with plain-English flags. Given only two parameters, the call semantics are adequately covered. The remaining gap is operational: error behavior for invalid or non-token addresses and how the x402 payment is settled are unaddressed.

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%, and the schema already documents both parameters including the 'base (default) or ethereum' option. The description adds little beyond that — it mentions Base/Ethereum and ERC-20, but no address-format validation rules or chain-specific caveats. Baseline 3 is appropriate when the schema carries the parameter burden.

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 specific resource and scope: 'ERC-20 token on Base or Ethereum', and enumerates the exact facts returned (name, symbol, decimals, supply, price/market cap, code size, proxy detection, owner status, risk level). That is far more than a restatement of the name. It stops short of differentiating itself from the sibling crypto_token_price, even though it also returns USD price and market cap, so an agent must infer which one to pick for price-only queries.

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 rather than stated: the field list makes clear this is for due-diligence/risk assessment on a token contract, and the explicit '$0.02 USDC (Base, via x402)' cost note gives the agent a real decision input before calling. However, there is no when-to-use/when-not statement and no routing to the obvious alternative (crypto_token_price) for callers who only want a quote.

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.

Resources