Skip to main content
Glama

Antigravity x402 & MCP Gateway

evaluate_token_risk_verdict

[0.008000 USDC via x402] Combines GoPlus contract security telemetry (honeypot, mintable, freeze authority, proxy, buy/sell tax, top-10 holder concentration) with live DexScreener USD liquidity, 24h volume, and FDV into a 0-100 safety verdict.

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": {
      "token_address": "<token_address>"
    },
    "name": "evaluate_token_risk_verdict"
  }
}

Input Schema

NameRequiredDescriptionDefault
chainNoTarget blockchain: 'base' (default), 'ethereum', 'bsc', 'polygon', 'arbitrum', or 'solana'.
token_addressYes0x EVM token contract address or case-sensitive Solana Base58 mint address.
x402_payment_signatureNoOptional base64 x402 PAYMENT-SIGNATURE header token (0.008000 USDC on Base eip155:8453 or Polygon eip155:137). Omit to receive the live x402 quote.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does disclose two non-obvious behaviors: that the call aggregates two external data providers (GoPlus and DexScreener) and that it is a paid call at 0.008 USDC via x402. It stops short of describing failure behavior (unsupported chain, unavailable upstream data) or latency/caching, which matters for a paid composite lookup.

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?

A single dense sentence with no filler; every clause (sources, metrics, output range) earns its place. The price tag is front-loaded ahead of the actual purpose, which is defensible for a paid tool but slightly delays what the tool does.

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

Completeness3/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 characterize the return value, and 'a 0-100 safety verdict' is thin — it does not say whether component scores, flags, or provider breakdowns come back. Chain support, address formats, and the payment quote flow are covered by the schema, and cost is covered in the description, so the remaining gap is the response shape.

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%, so chain values, address formats, and the x402 signature/quote flow are already documented structurally. The description adds no further parameter meaning — it does not, for example, tie specific parameters to specific telemetry sources or explain what happens when the chain is omitted.

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?

Uses a specific verb+resource ('evaluate_token_risk_verdict') and states exactly what is combined (GoPlus honeypot/mintable/freeze/proxy/tax/holder-concentration telemetry plus DexScreener USD liquidity, 24h volume, FDV) and what it produces (a 0-100 safety verdict). No sibling in the list does token contract safety scoring, so the agent can route here without ambiguity.

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?

The purpose implies the usage context (screen a token's contract and market risk before exposure), but the description never states when to prefer it over alternatives, when not to use it, or any prerequisites beyond cost. The one usage-adjacent fact given is the price bracket, which is helpful but not guidance.

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.