Skip to main content
Glama
yantrix-ai

@praveen030686/data-apis-mcp

Get Crypto AI Report

crypto_ai_report
Read-onlyIdempotent

Generate AI-powered cryptocurrency investment analysis reports with price action, fundamentals, and outlook insights for informed trading decisions.

Instructions

Get a Claude AI-written investment analysis report for any cryptocurrency. Includes price action, fundamentals, and outlook. Costs $0.25 USDC per request via x402 on Base.

Input Schema

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

Implementation Reference

  • Implementation of the 'crypto_ai_report' tool. It is registered on the server and its handler fetches data from a Crypto API endpoint.
    server.registerTool(
      "crypto_ai_report",
      {
        title: "Get Crypto AI Report",
        description: `Get a Claude AI-written investment analysis report for any cryptocurrency. Includes price action, fundamentals, and outlook.
    Costs $0.25 USDC per request via x402 on Base.`,
        inputSchema: {
          symbol: z.string().min(1).max(10).describe("Crypto symbol (e.g., BTC, ETH, SOL)"),
        },
        annotations: { readOnlyHint: true, destructiveHint: false, idempotentHint: true, openWorldHint: true },
      },
      async ({ symbol }) => {
        const data = await apiFetch(`${CRYPTO_API}/api/v1/llm-report/${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 $0.25 USDC cost per request and payment method (via x402 on Base). Annotations already cover read-only, open-world, idempotent, and non-destructive aspects, so the description appropriately focuses on monetization details not captured in structured fields.

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 perfectly concise with two sentences: the first states the core functionality, the second provides critical cost information. Every word earns its place, and the structure is front-loaded with the main purpose.

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 tool with rich annotations (readOnlyHint, openWorldHint, idempotentHint, destructiveHint) and no output schema, the description provides good context about what the tool returns (investment analysis report with specific components) and critical cost information. It could mention report format or length for full completeness.

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?

With 100% schema description coverage, the schema already fully documents the single 'symbol' parameter. The description doesn't add any parameter-specific information beyond what's in the schema, but this is acceptable given the comprehensive schema coverage. The baseline 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 tool's purpose: 'Get a Claude AI-written investment analysis report for any cryptocurrency' with specific components ('price action, fundamentals, and outlook'). It distinguishes from siblings like crypto_get_price (price only) and crypto_deep_analysis (different analysis type).

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 about what the tool provides (AI-written investment analysis report), but doesn't explicitly state when to use it versus alternatives like crypto_deep_analysis or finance_ai_report. The cost disclosure helps with usage decisions but doesn't provide comparative guidance.

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