Skip to main content
Glama
yantrix-ai

@praveen030686/data-apis-mcp

Get Crypto Price

crypto_get_price
Read-onlyIdempotent

Retrieve real-time cryptocurrency price data including 24-hour changes, trading volume, market capitalization, and 52-week price ranges for 53 supported symbols.

Instructions

Get real-time cryptocurrency price data including 24h change, volume, market cap, and 52-week range. Costs $0.01 USDC per request via x402 on Base. Supports 53 symbols: BTC, ETH, SOL, USDC, DOGE, AVAX, LINK, ADA, DOT, MATIC, UNI, AAVE, ATOM, NEAR, XRP, LTC, SHIB, ARB, OP, PEPE, BONK, SUI, SEI, TIA, JUP, WLD, TON, and more.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
symbolYesCrypto symbol (e.g., BTC, ETH, SOL, PEPE)

Implementation Reference

  • The handler function for 'crypto_get_price' which fetches price data from the API based on the provided symbol.
    async ({ symbol }) => {
      const data = await apiFetch(`${CRYPTO_API}/api/v1/price/${symbol.toUpperCase()}`);
      return { content: [{ type: "text", text: JSON.stringify(data, null, 2) }] };
    }
  • src/index.ts:53-69 (registration)
    Registration of the 'crypto_get_price' tool, including its schema and definition.
    server.registerTool(
      "crypto_get_price",
      {
        title: "Get Crypto Price",
        description: `Get real-time cryptocurrency price data including 24h change, volume, market cap, and 52-week range.
    Costs $0.01 USDC per request via x402 on Base.
    Supports 53 symbols: BTC, ETH, SOL, USDC, DOGE, AVAX, LINK, ADA, DOT, MATIC, UNI, AAVE, ATOM, NEAR, XRP, LTC, SHIB, ARB, OP, PEPE, BONK, SUI, SEI, TIA, JUP, WLD, TON, and more.`,
        inputSchema: {
          symbol: z.string().min(1).max(10).describe("Crypto symbol (e.g., BTC, ETH, SOL, PEPE)"),
        },
        annotations: { readOnlyHint: true, destructiveHint: false, idempotentHint: true, openWorldHint: true },
      },
      async ({ symbol }) => {
        const data = await apiFetch(`${CRYPTO_API}/api/v1/price/${symbol.toUpperCase()}`);
        return { content: [{ type: "text", text: JSON.stringify(data, null, 2) }] };
      }
    );
Behavior4/5

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

The description adds valuable behavioral context beyond annotations: it discloses the cost per request ($0.01 USDC via x402 on Base) and the scope of supported symbols (53 symbols listed). Annotations already indicate it's read-only, non-destructive, idempotent, and open-world, but the description enhances this with practical details like pricing and symbol support, without contradicting annotations.

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 front-loaded with key information (price data details, cost, symbol support) in three concise sentences. Each sentence earns its place by providing essential context without redundancy, making it efficient and well-structured for quick understanding.

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?

Given the tool's moderate complexity (single parameter, no output schema) and rich annotations, the description is mostly complete. It covers purpose, cost, and symbol scope, but lacks details on response format (e.g., structure of returned price data) and error handling, which could be useful for an agent invoking the tool effectively.

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, with the 'symbol' parameter well-documented in the schema itself (e.g., type, length, examples). The description adds minimal semantics by listing example symbols (BTC, ETH, SOL, PEPE) and noting support for 53 symbols, but this mostly reinforces what the schema already provides, aligning with the baseline score for high schema coverage.

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 tool's purpose with a specific verb ('Get') and resource ('real-time cryptocurrency price data'), listing detailed data points like 24h change, volume, market cap, and 52-week range. It distinguishes itself from sibling tools (e.g., 'crypto_ai_report', 'finance_stock_price') by focusing on crypto price data rather than analysis, reports, or other asset types.

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?

The description provides clear context for usage by specifying the supported symbols (e.g., BTC, ETH) and cost ($0.01 USDC per request), which helps determine when to use it. However, it does not explicitly state when not to use it or name alternatives among sibling tools (e.g., 'crypto_deep_analysis' for more detailed insights), leaving some guidance gaps.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/yantrix-ai/x402-apis-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server