Skip to main content
Glama

BitTalk News

get_waves

Read-onlyIdempotent

Elliott waves: the current count for a timeframe and closed counts (played out / invalidated) with wave points. timeframe — D1 or H1; limit — up to 30 recent counts. Analysis / Elliott-wave markup, NOT investment advice. 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_waves"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNoen
assetYes
limitNo
timeframeNoD1

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / lang
      Added value: +{
      +  "default": "en",
      +  "title": "Lang",
      +  "type": "string"
      +}
  2. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds real value on top by disclosing the returned content (current count, closed counts marked played out / invalidated, wave points) and the cap of 30 recent counts.

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

Conciseness4/5

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

Dense, front-loaded, and free of filler — the resource and return content come first, then per-parameter notes. The telegraphic dash style is slightly terse but every clause carries information.

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 and 0% schema description coverage, the description does the heavy lifting and mostly succeeds: it explains the return payload, the timeframe vocabulary, and the limit cap. It falls short only on the required asset parameter and on whether closed counts are always included or subject to limit.

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 coverage is 0%, so the description must carry the parameters, and it documents three of four: timeframe accepts D1 or H1, limit is capped at 30 recent counts, and lang is ru/en defaulting to en. The required 'asset' parameter is left entirely unexplained, which is the only material gap.

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?

Opens with a specific resource (Elliott wave counts) and states exactly what is returned: the current count for a timeframe plus closed counts (played out / invalidated) with wave points. An agent can distinguish this from get_candles, get_levels, or get_forecast by the resource alone, though the description never explicitly names those alternatives.

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 infers this tool is for Elliott-wave analysis from the first clause. There is no statement of when to prefer it over siblings, no preconditions, and the 'NOT investment advice' line is a disclaimer rather than routing guidance.

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