Skip to main content
Glama

Pre-trade token report (x402)

pretrade_full_report

Read-onlyIdempotent

$0.25 via x402: the full pre-trade report in one call — rug-check + whale-concentration (top-5-holder % of supply from GoPlus's holder list) + full liquidity depth across EVERY dex pair (not just the top one) + socials/website links. Same free upstreams as the $0.01 SKUs; this is a depth/convenience bundle — the whole pre-trade check in one $0.25 call.

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

Input Schema

NameRequiredDescriptionDefault
chainNoethereum|base|bsc|polygon|arbitrum|optimism|avalanche (default ethereum)
addressYesToken contract address 0x...
x_paymentNox402 payment payload (base64) to settle this call; omit to receive the payment terms first

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint, so the safety profile is covered. The description adds genuine context beyond that — the x402 price, that it draws on the same free upstreams as the cheap SKUs, and that liquidity is aggregated across EVERY pair rather than the top one. It does not cover latency, failure modes, or what happens if a chain/address is unsupported.

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?

Essentially one front-loaded sentence that leads with the price model, then the deliverable, then the differentiation from cheaper SKUs. Dense but every clause carries meaning; the '$0.01 SKUs' and 'depth/convenience bundle' framing is mildly repetitive but functional.

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?

There is no output schema, so the description carries the burden of explaining what comes back — and it does, by enumerating the four report components and clarifying that whale concentration is expressed as top-5-holder % of supply. Enough to call it correctly, though it omits response shape details (nesting, field names) and any error behavior.

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%: chain, address and x_payment are all documented in the schema, including the enum-like chain list and the omit-to-receive-terms behavior. The description adds no parameter-level detail (no address format hints, no chain caveats), so the baseline of 3 for high-coverage schemas applies.

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?

Names a specific deliverable (a bundled pre-trade report) and enumerates exactly what it contains: rug-check, top-5-holder concentration from GoPlus, liquidity depth across every dex pair, and socials/website links. It also distinguishes itself from the cheaper '$0.01 SKUs' by framing this as a depth/convenience bundle, so an agent can tell it apart from token_security_check or dex_token_data without opening schemas.

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?

Clear context is given: use this when you want the whole pre-trade check in one call at $0.25 rather than assembling pieces from the cheaper SKUs. It stops short of explicit when-not-to-use guidance or naming the specific cheaper siblings to route to instead, so the agent must infer that a single-field lookup should use a lighter tool.

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