Skip to main content
Glama

sol_token_verdict

Read-onlyIdempotent

One call → SAFE / CAUTION / AVOID for any Solana (SPL) token — token-verdict for Solana — one call → SAFE / CAUTION / AVOID for any SPL mint: mint & freeze authority (the Solana seize/freeze analog), Token-2022 extensions (permanent-delegate seize, transfer-hook honeypot, non-transferable, frozen-by-default), Jupiter sellability (buy-but-not-sell = honeypot) and RugCheck LP-lock + concentration. Same output shape as the Base hero. An unrunnable gating read is UNKNOWN, not charged. Not advice. Required input: mint. Priced $0.03 per call over x402 on Base; send a prepaid x-credit-token header for unlimited calls, or get 1 free call/day per tool. No API key required.

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

Input Schema

NameRequiredDescriptionDefault
mintYesSolana SPL mint address

Output Schema

NameRequiredDescriptionDefault
dataNoThe result payload. Shape is service-specific; every field is documented in the tool description.
serviceNoThe service id that answered.
checkedAtNoISO-8601 timestamp of when the underlying reads were taken.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior5/5

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

Beyond the annotations (read-only, idempotent, open-world, non-destructive), it discloses the payment model ($0.03 per call over x402 on Base), the prepaid x-credit-token alternative, a free tier, that no API key is needed, and that failed gating reads are UNKNOWN rather than charged. It also flags the result is informational only ('Not advice'), which is meaningful for how an agent should relay it.

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

Conciseness3/5

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

The verdict outcome is front-loaded, but the first sentence duplicates the same 'one call → SAFE / CAUTION / AVOID' and 'token-verdict for Solana' phrasing twice. The pricing/access detail is dense and useful, yet the redundancy wastes the most valuable opening space.

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?

An output schema exists, so return values need no explanation, and the description covers pricing, auth, failure handling, and the checks performed. What's missing is a crisp steer toward or away from sibling verdict/risk tools, but for a one-parameter read tool this is close to complete.

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% and the single parameter already documents 'Solana SPL mint address'. The description only repeats that mint is required, adding no format, validation, or interpretation detail beyond the schema. Baseline 3 applies 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?

The description states a specific verb and resource: it returns a SAFE / CAUTION / AVOID verdict for any Solana SPL mint, and enumerates the concrete checks (mint/freeze authority, Token-2022 extensions, Jupiter sellability, RugCheck LP-lock). It also implicitly distinguishes itself from the Base counterpart ('Same output shape as the Base hero'), but the opening is restated twice, which blunts the clarity.

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?

Scope is clear ('for any Solana (SPL) token', 'Required input: mint'), and failure semantics are noted ('An unrunnable gating read is UNKNOWN, not charged'). However, it never explicitly says when to prefer this over siblings like sellability or token_risk, and gives no when-not guidance.

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