Skip to main content
Glama
Sign In
coinopai-mcp

coinopai-mcp

by forgemeshlabs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

get_crypto_forecast

Get an honest 80% prediction interval for crypto prices (BTC, ETH, SOL, XRP, ADA) with point return and upside probability. Conformal calibration ensures reliable coverage for $0.05 USDC.

Instructions

Conformally-calibrated price forecast: an honest 80% prediction interval (range_80, ~0.80 empirical coverage) plus point return and upside probability for BTC/ETH/SOL/XRP/ADA. Directional bias is supporting context; the calibrated range is the validated product. Costs $0.05 USDC.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_crypto_forecast"
  }
}

Input Schema

NameRequiredDescriptionDefault
symbolNoSymbol: BTC, ETH, SOL, XRP, ADA (default: BTC)
affiliate_idNoOptional Pyrimid affiliate ID (af_xxxxx). Affiliate earns a commission from within the listed price — no extra cost to you.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior4/5

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

No annotations exist, so the description carries full burden. It discloses the calibrated nature ('honest 80% prediction interval'), the cost, and that directional bias is supporting context. It could mention rate limits or authentication, but for a forecast tool, it is sufficiently transparent about behavior.

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?

Every sentence is informative and no wasted words. The description is front-loaded with the key output type and then expands on specifics. It earns its space efficiently.

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?

With no output schema, the description adequately describes return values (range_80, point return, upside probability) and the empirical coverage. It omits error conditions or authentication details, but for a simple read-like tool with optional parameters, it is largely complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema covers both parameters 100%. Description adds value beyond schema by explaining the cost, the calibrated interval, and that affiliate_id earns commission without extra cost. This enriches the meaning of the parameters for the agent.

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 uses specific verbs and resources: 'Conformally-calibrated price forecast' and lists exact outputs (80% prediction interval, point return, upside probability). It clearly distinguishes from sibling tools like get_crypto_signals and get_crypto_decision by emphasizing the calibrated range and cost.

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?

Provides clear context: directional bias is supporting but the calibrated range is the validated product, and costs $0.05 USDC. While it doesn't explicitly state when NOT to use it or name alternatives, it implies suitability for probabilistic price forecasting versus other signal or decision tools.

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