Skip to main content
Glama

Racketeer Pre-Trade Checks (Solana)

pretrade check

pretrade_check
Read-onlyIdempotent

Is this Solana token safe to buy? Rug check this mint before a swap. Should my agent trade this token? Quick SAFE / CAUTION / BLOCK verdict with reasons and a priority-fee estimate. Price $0.01 per call via x402 (USDC on Solana or Base); 10 free calls per IP per day. 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_check"
  }
}

Input Schema

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

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?

Beyond the readOnly/openWorld/idempotent annotations, the description discloses pricing ($0.01 per call via x402 in USDC on Solana or Base), a free tier (10 calls per IP per day), and critically that on unpaid calls the tool returns x402 payment instructions instead of data. That payment-fallback behavior is exactly the kind of thing an agent cannot infer from annotations and would otherwise misinterpret as a failure.

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 in the first two sentences and the payment/limit caveat is properly included rather than buried. The three consecutive rhetorical questions ('Is this... safe to buy?', 'Rug check this mint...', 'Should my agent trade this token?') restate the same intent and could be collapsed into one.

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 no output schema, the description still explains what comes back (verdict plus reasons plus a priority-fee estimate) and what comes back when payment is required instead. Combined with the free-tier limit and the required mint input, an agent has everything needed to invoke it and interpret the response.

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?

There is a single required parameter with 100% schema description coverage, including the address pattern and an example mint, so the schema carries the semantics. The description adds no additional meaning about the mint argument (e.g., that it must be a mint rather than a wallet or pool address is only implied by the schema), 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?

The description names a specific resource (a Solana SPL/Token-2022 mint) and action (rug check before a swap) and states the output shape: a SAFE / CAUTION / BLOCK verdict with reasons and a priority-fee estimate. An agent can tell instantly this is a pre-trade safety screen. It does not explicitly differentiate itself from the overlapping token_safety or pretrade_full_report siblings, so it stops short of a 5.

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?

Usage context is explicit: call this on a mint before a swap / when deciding whether an agent should trade a token. There is no explicit when-not guidance or named alternative for a deeper report, which keeps it at 4 rather than 5.

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