Skip to main content
Glama

Racketeer Pre-Trade Checks (Solana)

token safety

token_safety
Read-onlyIdempotent

Rug check this mint: GO / CAUTION / AVOID from on-chain authorities and Token-2022 extensions. 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": "token_safety"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/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/call via x402, USDC on Solana or Base), a rate limit (10 free calls per IP per day), and a non-obvious failure mode: when payment is required the tool returns x402 payment instructions instead of data. That last detail is exactly the kind of behavior an agent cannot obtain from annotations or schema and needs in order to interpret a response correctly.

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?

Purpose and output categories are front-loaded in the first sentence, followed by cost/rate-limit/failure behavior in the second, with the disclaimer last. The pricing sentence is dense but every clause (price, asset, chain, free tier) affects whether an agent should call it.

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?

For a one-parameter, read-only check with no output schema, the definition covers verdict categories, cost, quota, and the payment-required branch, which is enough to call and interpret it. It could say slightly more about what the three verdict levels are based on, but nothing essential to invocation 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 coverage is 100% and the single mint parameter is fully documented with a regex and an example, so the schema carries the semantics. The description only echoes "this mint" without adding format, chain, or validity details, which is the appropriate baseline when the schema does the work.

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?

"Rug check this mint: GO / CAUTION / AVOID from on-chain authorities and Token-2022 extensions" names a specific verb (rug check), the resource (an SPL / Token-2022 mint), and the output taxonomy, so an agent knows exactly what comes back. It stops short of differentiating itself from siblings like pretrade_check or pretrade_full_report, leaving the agent to infer that this one is mint-level rather than trade-level.

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?

Usage is implied by "rug check this mint" rather than stated as a condition, and no alternative tool is named for related checks. The description does clarify the payment/free-tier mechanics that gate a call, which is useful operational guidance, but it never says when to prefer this over a pretrade variant.

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