Skip to main content
Glama

Racketeer Pre-Trade Checks (Solana)

pretrade full report

pretrade_full_report
Read-onlyIdempotent

Full due-diligence report on a Solana token before trading: who can mint or freeze it, Token-2022 traps (transfer fee, permanent delegate, transfer hook, non-transferable), top holders, token age, fee percentiles and the exact rules used. Price $0.10 per call via x402 (USDC on Solana or Base). When payment is needed the tool returns x402 payment instructions instead of data. Not financial advice.

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": {
      "mint": "<mint>"
    },
    "name": "pretrade_full_report"
  }
}

Input Schema

NameRequiredDescriptionDefault
mintYesSPL / Token-2022 mint address (e.g. DezXAZ8z7PnrnRJjz3wXBoRgixCa6xjnB7YaB1pPB263)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Annotations declare readOnly/idempotent/open-world but say nothing about cost or failure modes; the description adds the critical behaviors: $0.10 per call via x402, payable in USDC on Solana or Base, and that the tool returns payment instructions instead of data when payment is required. That last point is exactly the kind of non-obvious behavior an agent needs to interpret an unexpected response, and the financial-advice disclaimer is a useful caveat.

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?

Front-loaded with the capability, then pricing, then payment-fallback behavior, then disclaimer — each sentence carries distinct information. The parenthetical Token-2022 trap list is dense but is genuinely informative rather than filler.

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?

With one simple parameter and no output schema, the description carries the burden of describing the return content, which it does by enumerating report sections. Payment behavior and the paid-call model are disclosed, leaving nothing material an agent needs before invoking it.

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 coverage is 100% — the single `mint` parameter is documented with a regex pattern and a concrete example address. The description adds no additional parameter meaning beyond "a Solana token," so the baseline 3 applies.

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?

States a specific verb and resource ("Full due-diligence report on a Solana token") and enumerates exactly what the report covers: mint/freeze authority, Token-2022 traps, holders, age, fee percentiles. It does not name or contrast with the sibling pretrade_check or token_safety, so an agent must infer that this is the comprehensive/higher-cost variant, but the contents list makes the tool's identity unmistakable.

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?

"before trading" gives a clear operational context for when to reach for it. There are no explicit exclusions or routing instructions against the cheaper siblings (pretrade_check, token_safety), so an agent cannot tell from this text alone when to prefer the cheaper check instead.

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