Skip to main content
Glama

BitTalk News

get_levels

Read-onlyIdempotent

Price levels for a market, top to bottom, with distance from price in %: targets, triggers, interest zones, Fibonacci, weekly pivots and invalidation levels. 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_levels"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNoen
assetYes

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

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description's useful contribution is disclosing the shape of the returned content (the six level categories and % distance) and a disclaimer, but it says nothing about timeframe, ordering guarantees, or whether levels are recomputed vs cached.

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?

Front-loaded with the resource and its contents, then the disclaimer, then the lang note. Dense and mostly waste-free, though the 'Analysis / Elliott-wave markup, NOT investment advice' clause sits between the payload and the parameter guidance and slightly disrupts the ordering.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/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% param coverage, the description must compensate; it partially does by listing returned level types, but omits the asset identifier format and the timeframe/context the levels apply to. For a simple read-only fetch the annotations cover safety, so only the asset ambiguity is a real hole.

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 carries the full burden. It handles lang well (values ru/en, default en), but the required 'asset' parameter is never explained — no hint whether it is a ticker, symbol, or internal id — leaving the one mandatory parameter ambiguous.

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 specific resource (price levels for a market) and enumerates exactly what is included: targets, triggers, interest zones, Fibonacci, weekly pivots, invalidation levels, each with % distance from price. It does not, however, distinguish itself from plausible siblings like get_waves or get_forecast — the phrase 'Analysis / Elliott-wave markup' actually makes overlap with get_waves less clear, not more.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use or when-not-to-use guidance and no alternative tool is named. The agent is left to infer that this is the levels tool simply from the resource name, with no condition selecting it over get_waves, get_forecast, or get_candles.

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