Skip to main content
Glama

Diogenes Web3, DeFi & 402 Security MCP

Solana SPL Token Metadata, Decimals & Authority Registry Lookup

inspect_solana_token_liquidity
Read-onlyIdempotent

Retrieves canonical Solana SPL token metadata including name, ticker symbol, decimal precision, and current mint/freeze authority addresses. Use when resolving SPL token decimals, ticker symbols, and registry metadata for portfolio or swap formatting; for computing a composite security risk score and binary should_transact verdict, use evaluate_solana_token_risk instead. Stateless read-only edge call (max 32 KB, 60 RPM): accepts 'mint' ('network' defaults to 'mainnet-beta'), supports '?demo=true' or x402 (20 sats), and returns HTTP 400 if invalid.

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

Input Schema

NameRequiredDescriptionDefault
mintYesBase58-encoded Solana SPL token mint address (e.g. 'EPjFWdd5AufqSSqeM2qN1xzybapC8G4wEGGkZwyTDt1v').
networkNoSolana cluster to query; defaults to 'mainnet-beta' when omitted.

Output Schema

NameRequiredDescriptionDefault
mintYesQueried Base58 SPL token mint address.
symbolYesCanonical token ticker symbol (e.g. 'USDC', 'SOL', 'JUP').
decimalsYesToken decimal precision used for raw lamport/atomic unit conversion.
authorities_renouncedYesTrue when both mint_authority and freeze_authority are null.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, yet the description still adds real behavioral facts: stateless edge call, 32 KB response cap, 60 RPM rate limit, default network, '?demo=true' or x402 payment of 20 sats, and an HTTP 400 failure mode for invalid input. That is well beyond annotation coverage.

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?

Front-loaded with the payload first and the exclusion routing second, and virtually every clause carries operational information. It is somewhat dense with parentheticals crammed into a single long sentence, which slightly hurts scannability.

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?

For a two-parameter read tool with an output schema, everything an agent needs to call it correctly is present: scope, alternative, auth/payment path, rate and size limits, and error behavior. Return-value details are correctly delegated to the output schema.

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 coverage is 100% and both parameters (base58 mint, network enum with default) are already fully documented in the schema. The description only restates that 'mint' is accepted and that 'network' defaults to mainnet-beta, adding no new semantics.

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?

Names a specific verb and resource set ('Retrieves canonical Solana SPL token metadata including name, ticker symbol, decimal precision, and mint/freeze authority addresses') and explicitly contrasts with the sibling evaluate_solana_token_risk. An agent can distinguish the two without opening a schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives an explicit when-to-use ('resolving SPL token decimals, ticker symbols, and registry metadata for portfolio or swap formatting') and a named alternative with its own condition ('for computing a composite security risk score and binary should_transact verdict, use evaluate_solana_token_risk instead').

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.