Skip to main content
Glama
yantrix-ai

@praveen030686/data-apis-mcp

Get Crypto Trading Signal

crypto_get_signal
Read-onlyIdempotent

Analyze cryptocurrency trading signals with confidence scores, momentum indicators, and sentiment data to inform investment decisions. Powered by x402 USDC micropayments on Base.

Instructions

Get enriched trading signal (BUY/HOLD/SELL) with confidence score, momentum indicators, and sentiment data. Costs $0.05 USDC per request via x402 on Base.

Input Schema

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

Implementation Reference

  • Registration and implementation of the "crypto_get_signal" tool. It fetches signal data from the CRYPTO_API and returns it as a JSON-formatted string.
    server.registerTool(
      "crypto_get_signal",
      {
        title: "Get Crypto Trading Signal",
        description: `Get enriched trading signal (BUY/HOLD/SELL) with confidence score, momentum indicators, and sentiment data.
    Costs $0.05 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/signal/${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?

Annotations already indicate read-only, non-destructive, idempotent, and open-world behavior. The description adds valuable context beyond annotations by disclosing the cost ($0.05 USDC per request via x402 on Base), which is critical for usage decisions. However, it does not mention rate limits, authentication needs, or response format details.

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 the core purpose in the first sentence and adds cost information in the second. Both sentences earn their place by providing essential operational and financial context without redundancy or fluff, making it highly efficient.

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 complexity (financial analysis with cost implications), annotations cover safety aspects, but there is no output schema. The description compensates by detailing the returned data (signal, confidence, indicators, sentiment) and cost, though it lacks information on response structure or error handling. For a tool with no output schema, this is reasonably complete but not exhaustive.

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 description coverage is 100%, with the parameter 'symbol' fully documented in the schema. The description does not add any parameter-specific semantics beyond what the schema provides, such as examples of valid symbols or constraints. With high schema coverage, the 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 specific action ('Get enriched trading signal') and resource (trading signal data), distinguishing it from siblings like crypto_get_price (price only) or crypto_ai_report (broader analysis). It specifies the signal type (BUY/HOLD/SELL) and additional data (confidence score, momentum indicators, sentiment data), making the purpose explicit and differentiated.

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 obtaining trading signals for cryptocurrencies, but does not explicitly state when to use this tool versus alternatives like crypto_deep_analysis or crypto_ai_report. No exclusions or prerequisites are mentioned, leaving the agent to infer context from the tool name and description alone.

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