Skip to main content
Glama

arb_token_verdict

Read-onlyIdempotent

One call → SAFE / CAUTION / AVOID for any Arbitrum token — token-verdict for Arbitrum (chain 42161) — one call → SAFE / CAUTION / AVOID for any token: honeypot, buy/sell tax, mintable supply, owner powers (reclaim/hidden owner), pausable transfers, blacklist, upgradeable proxy, source verification, LP-lock and top-10 holder concentration, from GoPlus. Same output shape as the Base hero. An unreadable security check is UNKNOWN, not charged. Not advice. Required input: address. Priced $0.03 per call over x402 on Base; send a prepaid x-credit-token header for unlimited calls, or get 1 free call/day per tool. No API key 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": "arb_token_verdict"
  }
}

Input Schema

NameRequiredDescriptionDefault
addressYesArbitrum token address

Output Schema

NameRequiredDescriptionDefault
dataNoThe result payload. Shape is service-specific; every field is documented in the tool description.
serviceNoThe service id that answered.
checkedAtNoISO-8601 timestamp of when the underlying reads were taken.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior5/5

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

Beyond the annotations (readOnly, idempotent, openWorld), the description discloses the pricing mechanics ($0.03/call over x402 on Base), the prepaid x-credit-token header for unlimited calls, 1 free call/day per tool, no API key needed, and — importantly — that unreadable checks return UNKNOWN and are not charged. It also names the upstream data source (GoPlus) and promises output-shape parity with the Base variant, which is exactly the kind of expectation-setting annotations cannot express.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The outcome is front-loaded, which is good, but the first two clauses duplicate each other and the payment/credit details crowd the middle of what should be a single crisp statement. Pricing and free-tier facts earn their place; the repeated 'one call → SAFE / CAUTION / AVOID' framing does not.

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?

For a one-parameter read-only tool with an output schema, the description covers the essentials: what verdict is produced, which signals feed it, the data source, cost and auth model, and failure semantics (UNKNOWN, uncharged). The only meaningful omission is routing guidance against the closely named risk/verdict siblings.

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?

There is a single parameter and schema coverage is 100%, with the schema itself describing 'address' as an Arbitrum token address. The description only reinforces that address is required, adding no format, checksum, or chain-prefix detail beyond the schema. Baseline 3 applies since the schema carries the semantic load.

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 verb and resource — returning SAFE / CAUTION / AVOID for an Arbitrum (chain 42161) token — and enumerates the checks behind that verdict (honeypot, taxes, mintable supply, owner powers, blacklist, proxy upgradeability, LP lock, holder concentration). That pins down the tool and its chain scope well enough to separate it from the Solana/Base/generic variants. It loses a point because the leading clauses restate the same idea twice ('token-verdict for Arbitrum' then 'one call → SAFE / CAUTION / AVOID for any token') rather than naming a concrete sibling it replaces.

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 through the chain qualifier (Arbitrum-only) and the 'Not advice' disclaimer, plus the note that an unreadable check yields UNKNOWN. There is no explicit statement of when to pick this over near-named alternatives such as arb_token_risk or arb_sellability, and no when-not guidance. The agent must infer selection from the chain scope alone.

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