APEX Runner Crypto Signals

bb_analysis

$0.007 — Bollinger Band analysis for a crypto pair. Returns band width, price position, squeeze detection, and EXPANDED/CONTRACTING/CONTRACTED label. Query param: ?pair=BTC

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

Input Schema

Name	Required	Description	Default
`pair`	No	Trading pair (default: BTC)	BTC

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 11, 2026

TDQS

C2.9/5.0

Behavior2/5

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

With no annotations, the description carries the full behavioral burden. It discloses the returned fields and the EXPANDED/CONTRACTING/CONTRACTED label, plus a cost, but omits critical analysis behavior such as timeframe, Bollinger period, standard-deviation multiplier, and data freshness.

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?

The description is a single compact sentence that front-loads the price and then the purpose. It is efficient and easy to scan, though leading with the $0.007 price before the tool's function slightly dilutes front-loading.

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 simple one-parameter analysis tool with no output schema, the description does list the main return values. However, it leaves out the timeframe and Bollinger calculation settings that materially affect interpretation, and provides no annotations to cover those gaps.

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 coverage is 100%, and the single pair parameter is fully documented in the schema with an enum and default. The description repeats the query syntax (?pair=BTC) but adds no semantic detail beyond the schema, so the baseline 3 applies.

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 specific verb and resource: 'Bollinger Band analysis for a crypto pair,' and lists the outputs (band width, price position, squeeze detection, label). This distinguishes it from siblings like volume_analysis or funding_rate, though it does not explicitly name an alternative.

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?

The description provides no when-to-use guidance, no exclusions, and no alternatives. An agent must infer that this is the right tool whenever Bollinger Band metrics are needed, without any routing help.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All APEX Runner Crypto Signals tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?