Skip to main content
Glama

token_verdict

Read-onlyIdempotent

Full Base token verdict for a token contract address. Pulls free public onchain data (Base RPC, DexScreener, GoPlus token security) and runs 10 weighted checks: contract code present, honeypot / cannot-sell flags, mintable supply and hidden owner, owner control surface (proxy, pausable transfers, modifiable taxes, ownership take-back, self-destruct), buy/sell taxes, holder concentration (top-10 share), liquidity depth across Base DEX pairs, liquidity locked/burned share, 24h trading activity, and token age. Returns machine-readable JSON LED BY A FAIL-CLOSED TRADE DECISION — GO / HOLD / BLOCK — plus a one-line plain-language verdict, a 0-100 score, an A-F grade, a risk level, the top flags, per-check pass/partial/fail/unknown with evidence, a token block (name, symbol, supply, holder count), a market block (price, liquidity, 24h volume/txns, main pair, age), the decision basis, and a per-source status map. FAIL-CLOSED: if any key data source fails or returns nothing, the decision can never be GO; if two or more fail, it is BLOCK. HONEST LIMITS: a point-in-time snapshot — liquidity, holders, and flags can change within minutes on young tokens; checks that cannot be evaluated return unknown, never guesses; this is a mechanical risk scan, not financial advice. Cost: $0.02 USDC on Base per call, paid via x402 — the caller's agent pays from its owner's approved wallet; no API key needed. Use this as a pre-trade screen before buying or quoting any Base token.

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

Input Schema

NameRequiredDescriptionDefault
addressYesBase token contract address (0x-prefixed, 40 hex chars), e.g. 0x4ed4E862860beD51a9570b96d89aF5E1B0Efefed

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Annotations only cover the safety profile (readOnly, idempotent, openWorld), and the description adds substantial context beyond that: $0.02 USDC per call via x402 paid from the caller's owner wallet, no API key required, fail-closed decision logic with explicit thresholds, and unknown rather than guessed results for unevaluable checks. It also discloses the point-in-time snapshot limitation, which is exactly the kind of behavioral caveat 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.

Conciseness4/5

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

The definition is long but front-loaded with purpose, then return shape, then failure semantics, then limits and cost. The fail-closed rule is stated twice (once inline with the decision, once as a standalone 'FAIL-CLOSED:' sentence), which is mild redundancy in an otherwise dense, well-ordered block.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/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 describe returns itself, and it does so thoroughly: decision, verdict line, score, grade, risk level, flags, per-check evidence, token block, market block, decision basis, and source status map. Cost, payment mechanism, and data-source failure behavior are all covered, leaving nothing an agent needs before calling.

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?

The single parameter has 100% schema description coverage including format and an example, so the schema carries the load and baseline 3 applies. The description only reinforces that the address is a Base token contract, adding no new syntax or constraint information.

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?

The description names a specific verb and resource ('Full Base token verdict for a token contract address') and enumerates the ten weighted checks it runs, so an agent knows exactly what the tool produces. The word 'Full' plus the comprehensive check list implicitly distinguishes it from the lite sibling without needing to name it.

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?

It gives an explicit usage context: 'Use this as a pre-trade screen before buying or quoting any Base token.' That is a clear when-to-use statement, but there are no when-not conditions and the lite alternative is never named, so the agent must infer when the cheaper sibling is preferable.

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.