Skip to main content
Glama

Token price

token_price
Read-only

Get current USD price for any Solana token by mint address. Returns price, symbol, and supply info. Costs $0.0005 USDC per call.

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": {
      "mintAddress": "<mintAddress>"
    },
    "name": "token_price"
  }
}

Input Schema

NameRequiredDescriptionDefault
mintAddressYesSolana token mint address (base58)

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 and openWorldHint, so safety is covered; the description adds genuinely new context: the return payload (price, symbol, supply) and a per-call cost of $0.0005 USDC, which materially affects agent invocation decisions. It doesn't disclose freshness/staleness or behavior on an invalid mint address.

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?

Three short sentences with zero waste; the core purpose is front-loaded, followed by return shape and cost. Every sentence carries distinct information.

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 one-parameter read-only tool with no output schema, the description covers purpose, return fields, and cost, which is nearly everything an agent needs. Minor gaps remain around data freshness and error handling for unresolvable 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 parameter is documented as a base58 Solana mint address, so the schema does the heavy lifting. The description only echoes "by mint address" without adding format, validation, or resolution semantics 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?

States a specific verb and resource ("Get current USD price") plus a precise scope ("any Solana token by mint address"), which separates it reasonably well from generic siblings like crypto_price and from metadata tools like token_metadata. It does not explicitly name a sibling it is not, so it stops short of full differentiation.

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 Solana-mint-address scoping implies when this tool applies, but there is no explicit when-to-use/when-not guidance and no named alternative (crypto_price, token_metadata, token_risk_score) despite a crowded sibling list. Usage must be inferred.

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