Skip to main content
Glama

BitTalk News

list_assets

Read-onlyIdempotent

All markets with a BitTalk News forecast: price, status phrase, main scenario and a link to the page. 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

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": "list_assets"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNoen

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

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and closed-world, so the safety profile is covered. The description adds domain caveats ('Analysis / Elliott-wave markup, NOT investment advice', 'not a trade signal') and says results include a link to the source page. It does not say how many markets are returned, ordering, or whether the list is ever truncated.

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?

The description is short, but the structure is poor: it opens with a noun phrase rather than a verb, and the 'light — status-markup colour (red — the decline outweighs); not a trade signal' fragment uses em-dash chaining that is hard to parse. Content earns its place, but the ordering and punctuation obscure it.

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?

For a one-optional-parameter read-only list with no output schema, the description does explain the returned fields (price, status phrase, main scenario, link) and the language option. Missing only secondary details such as result volume or ordering, which are minor here.

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 parameter, and it does: 'lang — ru or en; default en' supplies the allowed values and default that the bare string schema lacks. The only weakness is the stray 'light — status-markup colour' clause, which reads like a parameter explanation but matches no parameter in the schema and may confuse an agent.

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?

The description states a clear scope: 'All markets with a BitTalk News forecast', and enumerates the payload (price, status phrase, main scenario, page link). That is enough to tell it apart from fetch/get_candles, though it does not explicitly contrast with screener or get_forecast, which could also surface market lists.

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 named alternative among the siblings. An agent must infer that this is the discovery/catalog call and that get_forecast or get_waves should be used for detail. Nothing in the text states that routing.

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