Skip to main content
Glama

BitTalk News

get_forecast

Read-onlyIdempotent

Forecast for a market (BTC, ETH, XAU, …): main and alternative scenarios with targets and an invalidation level, near-term conditions, the big picture by week/day/4 hours, and price levels. Scenarios are Elliott-wave counts, not probabilities; the share of “similar days” is a past frequency. Analysis / Elliott-wave markup, NOT investment advice. light — status-markup colour (red — the decline outweighs); not a trade signal. lang — ru or en; default en.

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": {
      "asset": "<asset>"
    },
    "name": "get_forecast"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNoen
assetYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / lang / default
      Previous value: -"ru"New value: +"en"
  2. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already cover safety (readOnlyHint, idempotentHint, destructiveHint=false), and the description goes well beyond them by disclosing the semantics of the output: scenarios are wave counts not probabilities, the 'similar days' share is historical frequency, and 'light' is a status colour rather than a signal. That prevents an agent from badly misreading the result; it stops short of mentioning paging, errors, or unsupported assets.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Core purpose is front-loaded, but the sentence is a single run-on that pivots mid-stream from output contents to disclaimers to an unrelated 'light' colour note to the lang parameter, all joined by em-dashes with no labels. Every fact is relevant, yet the ordering makes the parameter notes easy to conflate with output-field descriptions.

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 takes on the job of describing what comes back, and it does so thoroughly (scenario structure, invalidation level, timeframe breakdown, price levels), which is the main risk for this tool. The remaining gaps — asset handling for unknown tickers and sibling relationships — are comparatively minor for a read-only forecast call.

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 0%, so the description must carry the parameters, and it partially does: 'a market (BTC, ETH, XAU, …)' conveys the asset domain and 'lang — ru or en; default en' conveys the language enum and default. However, the trailing 'light — status-markup colour' clause is a field note crammed into the parameter prose and can be misread as a third parameter, and neither param gets format or validation detail.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a concrete verb and resource ('Forecast for a market (BTC, ETH, XAU, …)') and enumerates the returned content: main and alternative scenarios, targets, invalidation level, near-term conditions, multi-timeframe picture, price levels. It doesn't name a sibling such as get_waves or get_levels, so the boundary with related tools is left implicit, but the forecast framing is unmistakable.

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?

Usage is only implied: an agent can infer 'call this to obtain a scenario forecast for an asset'. The description spends its guidance budget on interpretation caveats ('scenarios are Elliott-wave counts, not probabilities', 'NOT investment advice', 'not a trade signal') rather than on when to pick this over get_waves or get_levels, and names no alternatives or exclusions.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources