Skip to main content
Glama

Scan by a bot condition: what matches right now

condition_scan
Read-only

Check a condition in the Telegram bot's syntax against live data and list the pairs that match now, strongest first. Syntax: metrics funding (%/h), cut (minutes to settlement), vol (24h volume, 1M = $1M), oi, plus ranges and presets — e.g. funding>0.3 cut<30 vol>1M, hedge 0.3 (cross-exchange spread), squeeze, or a bare threshold 0.3. Returns the exact /watch command the bot accepts, so the user can subscribe to future matches. Rates are predictions for the next settlement.

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": {
      "condition": "<condition>"
    },
    "name": "condition_scan"
  }
}

Input Schema

NameRequiredDescriptionDefault
coinNoCoin ticker (BTC) or any (default: any = the market's 300 strongest pairs)
langNoLanguage of the summary and links: 'en' (default) or 'ru'
limitNoRows, default 10
conditionYesBot condition, e.g. funding>0.3 cut<30 vol>1M, or a preset like hedge 0.3

Output Schema

NameRequiredDescriptionDefault
dataYesCompact numbers the conclusion is based on, units named inside
linkYesLive page with the same data
summaryYesOne-line conclusion — quote this

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior3/5

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

Annotations only declare readOnlyHint=true, so the description carries the rest of the burden. It adds genuinely useful context beyond the annotations — results are ordered strongest-first, the response embeds the exact /watch subscription command, and rates are forward-looking predictions for the next settlement. It does not address failure behavior for malformed conditions or any rate/coverage limits, which matters for a live-scan tool.

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?

Three sentences, front-loaded with what the tool does and the sort order, then syntax, then return value. The syntax sentence is dense but every clause (metric definitions, preset names, examples) contributes usable information; no filler.

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?

An output schema exists, so return values needn't be explained, and the description correctly focuses on input syntax plus the one non-obvious output fact (the /watch command). Combined with a fully-described 4-parameter schema and a readOnly annotation, this is nearly complete; only error handling for invalid syntax is unaddressed.

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 100%, so the baseline is 3, but the description adds real meaning beyond the schema for the required 'condition' parameter: it defines the metric vocabulary (funding in %/h, cut as minutes to settlement, vol as 24h volume with 1M = $1M, oi), notes support for ranges and presets, and supplies four worked examples including a bare threshold. The coin/lang/limit parameters are left entirely to the schema, keeping this below 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 specific verb and resource ('Check a condition ... against live data and list the pairs that match now, strongest first'), including the sort order and the fact that matching is against live data. It does not explicitly distinguish itself from siblings such as spread_pairs or funding_events, so sibling differentiation is left to inference.

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 rather than stated: an agent can infer this is the tool for 'what matches right now under a bot condition.' Nothing says when to prefer this over spread_pairs or funding_events, and no exclusions are given; the guidance present is mostly syntax help rather than when-to-use 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