Skip to main content
Glama

SolGuard Solana Token-2022 Scanner & Safe-Swap Router

Audit Solana Token Forensics & Slippage

solana_token_forensic_audit
Read-onlyIdempotent

Live Solana Mainnet forensic honeypot & real-slippage audit: checks mintAuthority, freezeAuthority, Token-2022 extensions (permanentDelegate, transferHook, pausableConfig, nonTransferable, transferFeeConfig), DexScreener liquidity, and live Jupiter v1 1.0 SOL -> Token -> SOL round-trip impact in bps.

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

Input Schema

NameRequiredDescriptionDefault
mintYesSolana Base58 SPL or Token-2022 mint address
probeSolNoSOL probe size for round-trip quote (0.01 to 100 SOL, default 1.0)

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, openWorldHint=true, idempotentHint=true and destructiveHint=false, so the safety profile is covered. The description adds real value beyond that by disclosing that probes hit live Solana Mainnet and live Jupiter v1 routing, and by naming exactly which on-chain and market checks are performed. It omits failure modes (unlisted token, illiquid pool) and expected latency, keeping it short of a 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence with the operation and its scope stated first, followed by an enumerated list of checks. Every clause carries information; there is no filler or repetition.

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 two-parameter, single-purpose audit tool that carries full annotations, the description covers what is inspected and against which live sources. The remaining gap is the return shape — with no output schema, the agent is not told whether results come back as booleans, authority addresses, or a bps figure, nor how failures are reported.

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 both mint and probeSol are already documented in the schema and the baseline is 3. The description's mention of the '1.0 SOL -> Token -> SOL round-trip' explains what the probe size is actually measuring (round-trip price impact in bps), which adds a little meaning but no syntax or edge-case guidance beyond the schema.

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 gives a specific verb+resource: a live forensic honeypot and real-slippage audit of a Solana token mint, enumerated through concrete checks (mintAuthority, freezeAuthority, Token-2022 extensions, DexScreener liquidity, Jupiter round-trip impact). This is far more specific than a title restatement and is clearly distinct from the build_* transaction-building siblings, though it never explicitly names or contrasts an alternative.

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 only implied: an agent can infer this is a pre-trade safety/slippage check on a token mint, but the description never states when to call it versus when not to, nor any prerequisites or alternatives. Nothing is misleading, but nothing routes the agent explicitly either.

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