Skip to main content
Glama

Token security check

token_security
Read-only

Check if a Solana token is safe to trade. Returns rug pull detection, honeypot flags, freeze/mint authority, insider networks, transfer fees, and a risk score via RugCheck. Costs $0.005 USDC per call.

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": {
      "mintAddress": "<mintAddress>"
    },
    "name": "token_security"
  }
}

Input Schema

NameRequiredDescriptionDefault
mintAddressYesSolana token mint address (base58)

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 cover read-only and open-world traits, and the description adds real value on top: a specific per-call price ($0.005 USDC), the underlying data provider (RugCheck), and the exact risk categories returned. It stops short of saying anything about rate limits, failure behavior for invalid/illiquid mints, or whether paid calls can fail after charging.

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?

Three short sentences, front-loaded with the purpose, then the return contents, then the cost. Every sentence carries information an agent would otherwise have to guess at.

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?

With no output schema, the description does the work of listing returned signal types, and it discloses the price and provider, so an agent knows what it gets and what it costs. What's missing is small but real: no note on chain restriction beyond 'Solana', and no hint about latency or failure modes.

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?

The single parameter is fully documented in the schema ('Solana token mint address (base58)') at 100% coverage, so the description appropriately leaves it alone. It adds nothing about format edge cases, which is acceptable here but no more than baseline.

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?

States a specific verb and resource ('Check if a Solana token is safe to trade') and enumerates exactly what the response covers (rug pull, honeypot, freeze/mint authority, insider networks, transfer fees, risk score). It does not distinguish itself from close siblings like token_risk_score or token_holders, which an agent must differentiate on its own.

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 name and the 'safe to trade' framing, but there is no explicit when-to-use or when-not-to-use guidance and no mention of token_risk_score, the obvious overlapping alternative. The only routing signal an agent gets is that this one runs on Solana.

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