Skip to main content
Glama
Sign In
Alchemy MCP Server

Alchemy MCP Server

Official
by alchemyplatform
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Remote

fetchTokenPriceBySymbol

Retrieve current USD prices for multiple blockchain tokens by providing their ticker symbols like BTC or ETH, enabling quick price checks across assets.

Instructions

Get current USD prices for tokens by their ticker symbol (e.g. BTC, ETH)

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": {
      "symbols": "<symbols>"
    },
    "name": "fetchTokenPriceBySymbol"
  }
}

Input Schema

NameRequiredDescriptionDefault
symbolsYesA list of blockchaintoken symbols to query. e.g. ["BTC", "ETH"]

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior2/5

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

No annotations are provided, so the description carries full burden for behavioral disclosure. It only states the basic function without mentioning rate limits, data freshness, error handling for unknown symbols, or whether multiple tokens with the same ticker are handled. This is insufficient for safe invocation.

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 a single sentence of 11 words, front-loading the verb and resource. Every word is informative without redundancy, making it highly concise.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the simple one-parameter tool with no output schema, the description is minimally adequate. However, it lacks details on return format, error behavior, or network support, which would be expected for a price fetch tool. It scores 3 as it covers the core intent but misses useful context.

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?

The input schema has 100% description coverage for the 'symbols' parameter, clearly explaining it expects a list of token symbols. The description's mention of 'ticker symbol' reinforces but does not add new meaning beyond the schema, so baseline score of 3 is appropriate.

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 action: 'Get current USD prices for tokens by their ticker symbol'. It distinguishes from sibling fetchTokenPriceByAddress by specifying the method (symbol vs address) and includes an example (e.g. BTC, ETH).

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 for tokens with ticker symbols but does not explicitly state when to use this tool instead of fetchTokenPriceByAddress or other tools. No when-not or alternative conditions are provided, leaving the agent to infer based on parameter type.

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

Deploy Server

Other Tools