Skip to main content
Glama

Solana Signal

Solana token prices

token_prices
Read-only

Live USD prices, 24h change and liquidity for up to 100 Solana token mints in one call. Free tier 20/day per IP.

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": {
      "mints": "<mints>"
    },
    "name": "token_prices"
  }
}

Input Schema

NameRequiredDescriptionDefault
mintsYesToken mint addresses (e.g. So11111111111111111111111111111111111111112 for SOL)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered; the description adds the genuinely useful behavioral facts of a 20 requests/day per-IP free tier and a 100-mint batch ceiling. It stops short of saying how invalid or unknown mints are handled, which matters for a batch endpoint.

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?

Two short sentences, front-loaded with the payload contents and closed with the quota constraint. Nothing is redundant or padded.

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?

With no output schema, the description correctly compensates by listing the returned fields, and it discloses the rate limit, so an agent can call it correctly. The only real gap is error/partial-failure behavior for a batch of up to 100 mints.

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 mints parameter is fully documented including the regex and the SOL example, so the schema does the heavy lifting. The description's 'up to 100' merely restates maxItems and adds no format or addressing detail beyond the schema.

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 names the resource (Solana token mints) and enumerates the returned data (live USD price, 24h change, liquidity), which is more specific than the title alone. It doesn't explicitly contrast with token_risk or tx_explain, but the data-fields enumeration makes the distinction reasonably obvious.

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?

Usage is only implied: 'up to 100 ... in one call' signals batching and 'Free tier 20/day per IP' signals a quota, which tells an agent to batch rather than loop. There is no explicit when-to-use or when-not-to-use guidance relative to siblings such as token_risk.

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