Skip to main content
Glama

ChainGuard Web3 & MCP Shield

check_solana_token2022

Inspect Solana SPL / Token-2022 mint for PermanentDelegate drainers, TransferHooks, Mint/Freeze authority & RugCheck score.

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

Input Schema

NameRequiredDescriptionDefault
mintYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior2/5

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

With no annotations at all, the description carries the full burden. It lists the risk categories examined but says nothing about whether the check is read-only, that it depends on an external RugCheck lookup (availability/latency/rate limits), how failures are reported, or whether absence of findings means safe. For a security-judgment tool this leaves significant behavioral gaps.

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?

One front-loaded sentence that names the resource first and then the checks, with zero filler. Every listed item is a concrete signal the agent can act on.

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 one-parameter read tool with no output schema, the description does enough to convey what is inspected, but it never hints at the shape of the result (per-check verdicts vs. a single score) nor how an agent should interpret a RugCheck score. A short note on returned findings would make it complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0% and the single parameter 'mint' is undocumented in the schema. The description only obliquely implies the argument is a Solana mint address — it never states the expected format (base58 pubkey), whether Token-2022 vs legacy SPL matters, or what happens with an invalid address.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Specific verb ('Inspect') plus a concrete resource ('Solana SPL / Token-2022 mint') and an enumeration of the exact checks performed (PermanentDelegate drainers, TransferHooks, authority flags, RugCheck score). This clearly separates it from the EVM/MCP-oriented siblings without needing to name them.

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 the security-audit framing — an agent can infer this is the tool for vetting a Solana mint before interacting with it — but there is no explicit when-to-use/when-not guidance, no statement of prerequisites, and no mention of what to do for non-Token-2022 or non-Solana addresses.

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