Skip to main content
Glama

BitTalk News

screener

Read-onlyIdempotent

BitTalk News markets screener: market crypto (USDT pairs on Binance), ru (Moscow Exchange) or us (US); sort volume, change or change_abs; covered_only — only coins that have a forecast (forecast field). Analysis / Elliott-wave markup, NOT investment advice. 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": "screener"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNoen
sortNovolume
limitNo
marketNocrypto
covered_onlyNo

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.6/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 openWorldHint=false, so the safety profile is covered. The description adds that output is 'Analysis / Elliott-wave markup, NOT investment advice' and that covered_only restricts to coins with a forecast, but says nothing about result volume, pagination, or what a row contains beyond the forecast field.

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?

A single dense sentence front-loads the tool identity and then enumerates each meaningful option with a semicolon; there is no filler. The disclaimer costs a few words but is genuinely relevant for a forecasting tool.

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?

For a 5-parameter screening tool with no output schema, the description never characterizes the returned rows (fields beyond forecast, ordering guarantees, how limit interacts with results). It does enough to call the tool, but an agent cannot predict the response shape.

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 description coverage is 0%, so the description must carry the parameter meaning — and it supplies enum values the schema lacks: market = crypto/ru/us (with what each denotes), sort = volume/change/change_abs, covered_only = only coins with a forecast, lang = ru/en default en. Only 'limit' is left unexplained, which keeps it from a 5.

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+resource: a markets screener over three named markets (crypto USDT pairs on Binance, Moscow Exchange, US) with sortable metrics. It is clearly a screening/list tool and not a lookup like get_candles or get_forecast, though it never explicitly names a sibling to differentiate itself.

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 implied by the sorting/coverage options (screen markets by volume, change, or change_abs), but there is no explicit when-to-use or when-not-to-use guidance versus list_assets or search. No prerequisites or exclusions are stated.

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