Skip to main content
Glama

Crypto & Macro Market Data (Tanod)

get_solana_token_price

Read-onlyIdempotent

chainpeek: Get the USD price and liquidity of a Solana token by mint address. For large recent trades use get_large_solana_token_trades. Returns its USD price and the liquidity of its deepest pool. Spot price of one pool, computed from on-chain accounts, cached 15 s; Raydium, Orca and Meteora pools against USDC, USDT or SOL only; no pool is a 422 no_pool and an unreachable pool list or stale oracle a 503 (neither charged). Solana mainnet, confirmed commitment. A malformed input is a 422 before payment and a failing RPC read a 503 (neither charged). Typically 1-4 s. Price: USD 0.005. Free: 10 chain reads per IP per UTC day. Docs: https://tanod.dev/learn/solana-token-price-api.html

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

Input Schema

NameRequiredDescriptionDefault
mintYesSPL Token or Token-2022 mint address (base58) of the token to price.

Output Schema

NameRequiredDescriptionDefault
dexNo
mintNo
noteNo
poolNo
slotNo
as_ofNo
errorNoOnly on an error result: an object {code, message}, or the reason string of an x402 PaymentRequired object.
sourceNo
sol_usdNo
decimalsNo
price_usdNo
rpc_callsNo
quote_mintNo
other_poolsNo
quote_symbolNo
liquidity_usdNo
pools_checkedNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • removedInput schema / properties / mint / title
      Removed value: -"Mint"
    • removedInput schema / title
      Removed value: -"get_solana_token_priceArguments"
    • removedOutput schema / properties / other_pools / items
      Removed value: -{
      -  "properties": {
      -    "dex": {
      -      "type": [
      -        "string",
      -        "null"
      -      ]
      -    },
      -    "liquidity_usd": {
      -      "type": [
      -        "number",
      -        "null"
      -      ]
      -    },
      -    "pool": {
      -      "type": [
      -        "string",
      -        "null"
      -      ]
      -    },
      -    "price_usd": {
      -      "type": [
      -        "number",
      -        "null"
      -      ]
      -    }
      -  },
      -  "type": [
      -    "object",
      -    "null"
      -  ]
      -}
    • removedOutput schema / properties / sol_usd / properties
      Removed value: -{
      -  "confidence": {
      -    "type": [
      -      "number",
      -      "null"
      -    ]
      -  },
      -  "price": {
      -    "type": [
      -      "number",
      -      "null"
      -    ]
      -  },
      -  "publish_time": {
      -    "type": [
      -      "string",
      -      "null"
      -    ]
      -  }
      -}
  2. Added

TDQS

A4.3/5.0
Behavior5/5

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

Goes well past the readOnly/idempotent/openWorld annotations: 15 s cache TTL, mainnet with confirmed commitment, 1-4 s latency, specific failure codes (422 no_pool, 503 for unreachable pool list or stale oracle) and the fact that failures are not charged. Cost and free-tier limits are also disclosed.

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?

Front-loads purpose well, but the error-handling sentences are redundant: '422 before payment' and '503 … neither charged' appear twice in near-identical form. Length is otherwise justified by dense operational detail, but the duplicated billing/error sentence costs points.

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 single-parameter read tool with an output schema and full annotations, the description covers scope, exclusions, latency, caching, error semantics, cost and rate limits. Nothing an agent needs to decide or invoke correctly is missing.

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 the single 'mint' parameter is fully documented in the schema (base58 SPL Token or Token-2022 address, length and charset). The description only restates 'by mint address' and adds no format or edge-case detail beyond the schema, so the baseline of 3 applies.

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?

States a specific verb and resource ('Get the USD price and liquidity of a Solana token by mint address') and explicitly separates itself from the sibling 'get_large_solana_token_trades'. An agent can distinguish this from the generic 'get_token_price' by the Solana/mint scoping without opening the schema.

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?

Gives an explicit routing rule to the sibling for recent large trades, plus hard coverage limits (only Raydium/Orca/Meteora pools against USDC, USDT or SOL). It does not state when to prefer the generic 'get_token_price' or 'get_dex_price_candles', but the positive guidance and scope constraints are clear.

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.