Skip to main content
Glama

Solana Rent & Rug Shield MCP Gateway

Solana 10-Layer Pre-Buy Token Anti-Rug Audit (<120ms)

audit_solana_token_10_layer
Read-onlyIdempotent

<120ms pre-buy 10-layer Solana token safety gate over persistent keep-alive connections. Audits mint/freeze authorities, Token-2022 extensions (transfer fee, permanent delegate, transfer hook, default frozen), LP lock/burn status, top holder cluster concentration, exit liquidity solvency, Layer-8/9 Inner-CPI rent traps, pool age, and orderflow velocity. Includes 10 free pings and Solana x402 auto-upgrade.

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

Input Schema

NameRequiredDescriptionDefault
mintYesSolana SPL or Token-2022 token mint address (base58) to audit pre-buy.
walletNoOptional buyer Solana wallet public key (base58).
x_paymentNoOptional base64 or JSON Solana x402 payment payload (X-Payment / PAYMENT-SIGNATURE) for automatic HTTP 402 settlement.
pool_addressNoOptional DEX liquidity pool or pair address (base58).
pro_pass_tokenNoOptional X-Pro-Pass-Token from Option A ($1.99 / 0.026 SOL Unlimited Pro Pass).
payment_signatureNoOptional confirmed Solana transaction signature paying 89Sv5FvnMNRid1bn8y2Ti1vJPSxWxgiW9GSLsPpBnKK1 (0.026 SOL Option A or 0.0003 SOL Option B).

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?

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so safety is covered. The description adds genuinely non-obvious behavior: latency under 120ms over persistent keep-alive connections, an included quota of 10 free pings, and automatic x402 settlement once that quota is exhausted. It stops short of explaining what happens when payment is absent or how failures are surfaced.

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?

Two sentences, with the latency claim and tool category front-loaded before the audit-checklist detail. The checklist is dense and jargon-heavy (Layer-8/9 Inner-CPI rent traps) but each item conveys a distinct check, so little is wasted. Readability suffers mildly from packing everything into one long cumulative sentence.

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?

For a 6-parameter tool with no output schema, the description fully explains what is inspected but says nothing about what comes back (a score, per-layer verdicts, flags, pass/fail) or how the payment fallback behaves on rejection. Given the complexity and the absence of an output schema, the return contract is a real gap an agent must guess at.

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 all six parameters, including the payment and pro-pass fields, are already documented in the input schema. The description adds no parameter-level meaning beyond that, such as when to supply pool_address or how x_payment interacts with payment_signature. Baseline 3 is appropriate when the schema does the heavy lifting.

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 opens with a specific verb+resource: a pre-buy safety gate that audits a Solana token mint, and it enumerates the exact checks (mint/freeze authorities, Token-2022 extensions, LP lock/burn, holder concentration, exit liquidity, rent traps, pool age, orderflow). That is far more specific than the name alone. It never names the siblings (simulate_solana_tx_drain, scan_wallet_unclaimed_sol), so the differentiation is inferable from the resource noun rather than stated.

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?

The recurring 'pre-buy' framing gives a clear when-to-use context: run this before acquiring a token to screen for rug vectors. It does not state when not to use it, nor does it direct the agent to any alternative for post-buy or wallet-level checks. Clear trigger context, no exclusions.

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.