Skip to main content
Glama

Solana token report

solana_token_report
Read-onlyIdempotent

Solana token rug & safety report: mint/freeze authorities, top holders, Jupiter exit ladder and verdict. $0.01 per call over x402 (USDC on Arc, Base or Solana, or XNT on X1). Call once without payment for terms, sign with your own wallet, call again with payment.

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_report"
  }
}

Input Schema

NameRequiredDescriptionDefault
mintYesSolana token mint address (base58)
paymentNosigned x402 payment payload (PAYMENT-SIGNATURE).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior5/5

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

Beyond the readOnly/idempotent/non-destructive annotations, the description discloses the priced nature of the call ($0.01 per call), the accepted payment rails (USDC on Arc/Base/Solana, XNT on X1), and the required two-phase terms-then-payment flow. Those are exactly the operational facts an agent cannot infer from the annotations alone.

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?

Three dense sentences, front-loaded with what the report contains before moving to cost and the call protocol. The payment-rail enumeration is long but each clause carries necessary information; there is no filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, yet the description previews the return contents (authorities, holders, exit ladder, verdict), and it covers cost, payment method, and the multi-step invocation protocol. For a two-parameter, priced lookup tool this is complete enough to call correctly.

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

Parameters4/5

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

Schema coverage is 100%, so the schema already defines `mint` and `payment`; the baseline would be 3. The description adds real meaning for `payment` by explaining it is obtained through a first unpaid call and wallet signing, which is more than the terse 'signed x402 payment payload' schema text conveys.

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-plus-resource framing ('Solana token rug & safety report') and enumerates the concrete contents: mint/freeze authorities, top holders, Jupiter exit ladder and verdict. The 'Solana' qualifier implicitly separates it from chain-specific siblings such as x1_token_report and arc_token_check, but it never states that distinction outright.

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?

It gives explicit procedural guidance for the payment handshake: call once without `payment` for terms, sign with your own wallet, then call again with `payment`. That is clear context for how to invoke it, though it offers no guidance on when to prefer this report over a sibling like base_token_verdict or token_lookup.

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