Skip to main content
Glama

token_verdict

Read-onlyIdempotent

SAFE / CAUTION / AVOID for any Base token — one call — One call, one answer: SAFE / CAUTION / AVOID for any Base token. Runs the full pre-trade safety stack (honeypot, sell-tax, owner powers, exit-liquidity, deployer, B20 seize/freeze) and distils it to a single plain-language verdict with the reasons behind it, a confidence, a max safe size and a shareable card. The depth of pre-trade-bundle, reduced to the one decision an agent needs before it buys. A gating check that could not run is UNKNOWN, not charged. Not financial 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": "token_verdict"
  }
}

Input Schema

NameRequiredDescriptionDefault
addressYesToken contract address
amountUsdNoTrade size in USD (optional — sizes the max-safe check)

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

A4.4/5.0
Behavior5/5

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

Goes well beyond the supplied read-only/idempotent annotations: it enumerates the checks performed (honeypot, sell-tax, owner powers, exit-liquidity, deployer, B20 seize/freeze), describes the degradation policy (failed gate → UNKNOWN, not charged), the pricing model ($0.03/call over x402, prepaid x-credit-token header, 1 free call/day, no API key), and the payload contents including a shareable card. It even adds a 'Not financial advice' caveat. No contradiction with annotations.

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 core purpose is front-loaded and each later clause (checks, degradation, pricing) earns its place for a paid gating tool. However, the opening repeats itself almost verbatim ('SAFE / CAUTION / AVOID for any Base token — one call — One call, one answer: SAFE / CAUTION / AVOID for any Base token'), which is wasted space.

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?

For a paid, open-world, read-only verdict tool this is complete: required input is named, cost/auth path is spelled out, degradation behavior is disclosed, and an output schema exists so return values need no further explanation. Nothing an agent needs to invoke it correctly is missing.

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 both parameters already carry descriptions, so the schema does the heavy lifting. The description only restates 'Required input: address' and alludes indirectly to the optional amountUsd via 'max safe size'; it adds no syntax, format, or address-validation detail beyond the schema. Baseline 3 is appropriate.

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?

States a concrete verb+resource ('Runs the full pre-trade safety stack ... distils it to a single plain-language verdict') with explicit scope ('any Base token') and a clear output shape (SAFE/CAUTION/AVOID plus reasons, confidence, max safe size). It also distinguishes itself from the deeper bundle report by positioning its result as the one decision, so an agent can tell it apart from a full risk/audit tool without opening a schema.

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?

Frames the use case tightly ('the one decision an agent needs before it buys') and clarifies the gating semantics — an unrunnable check yields UNKNOWN and isn't charged. It does not explicitly name when to prefer a deeper sibling report (e.g. a full risk/audit tool) versus this distilled verdict, so the when-not guidance is implicit.

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