Skip to main content
Glama

zato crypto data

Token risk facts: proxy, owner/renounced, mint/pause/blacklist/fee functions in bytecode (Ethereum, Base)

token_risk
Read-only

Facts about an ERC-20 token contract: proxy, owner/renounced, mint/pause/blacklist/fee functions, supply. No score. Price: $0.003 USDC per call (x402, Base).

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

Input Schema

NameRequiredDescriptionDefault
networkNo"ethereum" or "base" (default)
contractYesERC-20 token contract

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds genuinely new context beyond them: the per-call price of $0.003 USDC via x402 on Base, and the clarification that no composite score is returned. It omits failure behaviour for non-token or unverified addresses and any latency or rate-limit expectations.

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?

Two compact sentences that front-load the payload of returned facts and then the cost and the no-score caveat. Nothing is redundant. The telegraphic list style is dense but readable, and the cost note is correctly placed last.

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?

With no output schema, the description carries the burden of describing returns, and it does so by enumerating the checked properties. For a two-parameter read-only tool this is close to sufficient; the main gap is behaviour on unsupported networks or addresses that are not token contracts.

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%, with both 'network' and 'contract' documented inline including examples and the default, so the baseline is 3. The description itself adds no parameter-level meaning beyond restating that the input is an ERC-20 contract; the network dimension is only implied via the title's chain list.

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 the resource (an ERC-20 token contract) and enumerates exactly the facts returned: proxy, owner/renounced, mint/pause/blacklist/fee functions, supply. That is specific enough for an agent to know what it gets back. It stops short of distinguishing itself from plausible neighbours such as contract_info or preflight, so it does not reach a 5.

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?

There is no explicit when-to-use guidance and no named alternative. The only scoping signal is the negative constraint 'No score', which tells the agent this is not a risk rating but does not say which sibling to call instead. An agent must infer the selection context from the title's chain list.

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