solana-mcp-server

Overview Schema Source Related Servers Discussions Admin

get_token_price

Retrieve the current USD price for any Solana token by providing its symbol or mint address, using Jupiter as the primary source and CoinGecko as a fallback.

Instructions

Aktuellen USD-Preis eines Solana-Tokens abfragen.

Nutzt Jupiter als primäre Quelle, CoinGecko als Fallback.

Args: token: Token-Symbol (z.B. "SOL", "BONK") oder Mint-Adresse

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": {
      "token": "<token>"
    },
    "name": "get_token_price"
  }
}

Input Schema

Name	Required	Description	Default
`token`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Mar 18, 2026

TDQS

A4.3/5.0

Behavior4/5

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

With no annotations provided, the description carries full burden and adds valuable behavioral context: it discloses the dual data source strategy (Jupiter primary, CoinGecko fallback) and specifies the currency (USD). However, it doesn't mention rate limits, error handling, or response format details that would be helpful for an agent.

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?

The description is efficiently structured with a clear purpose statement, behavioral details, and parameter explanation in just three lines. Every sentence earns its place, and information is front-loaded with the core functionality stated first.

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?

For a single-parameter query tool with no annotations and no output schema, the description provides good context: purpose, data sources, parameter semantics. However, it doesn't describe the return value format (e.g., numeric price, timestamp, source attribution) which would help the agent interpret results.

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

Parameters5/5

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

With 0% schema description coverage and only 1 parameter, the description fully compensates by explaining the 'token' parameter accepts either a token symbol (e.g., 'SOL', 'BONK') or a mint address. This adds crucial semantic meaning beyond the bare schema's string type.

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?

The description clearly states the specific action ('Aktuellen USD-Preis...abfragen' - query current USD price) and resource ('eines Solana-Tokens' - of a Solana token). It distinguishes from siblings like 'get_token_info' (general info) and 'get_wallet_balance' (balance check) by focusing exclusively on price retrieval.

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?

The description implies usage context by specifying it's for Solana tokens and mentions data sources (Jupiter primary, CoinGecko fallback), but doesn't explicitly state when to use this tool versus alternatives like 'get_token_info' (which might include price) or 'compare_yields' (which involves yield comparison). No explicit when-not-to-use guidance is provided.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server