Skip to main content
Glama

APEX Runner Crypto Signals

capital_rotation_signal

$0.007 — Detect capital rotation state: BTC_ACCUMULATION, ALT_SEASON_EARLY, ALT_SEASON_LATE, RISK_OFF, RECOVERY, or CHOPPY. Based on BTC dominance trend, F&G, whale positioning, and funding rates. Returns recommended allocation per coin.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full disclosure burden. It does add real context by naming the inputs feeding the classification (BTC dominance trend, F&G, whale positioning, funding rates) and stating that it returns a recommended allocation per coin, but it omits whether the signal is computed live versus cached, how frequently regimes flip, and any reliability or staleness caveats an agent would need before acting on the output.

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 tight sentences: the price marker, the detection purpose with enumerated states, the data sources, and the return shape. The input-source sentence earns its place by explaining where the classification comes from. Slight redundancy between 'detect state' and the value list, but nothing is wasted.

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 zero-parameter analytical tool with no output schema, the description covers what is needed to select and invoke it: purpose, taxonomy of results, underlying data, and return shape. It falls short only on how 'recommended allocation per coin' is structured and whether the output should be treated as a regime label or an actionable allocation.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate and the baseline is a 4. The enumerated state values are a useful bonus even though the input schema is empty.

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 ('Detect capital rotation state') and enumerates the six possible regime outputs, which gives an agent a concrete picture of what it gets back. It does not explicitly distinguish itself from neighbors like btc_dominance or altcoin_season, which clearly overlap in subject matter, so full marks are not warranted.

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 is purely a capability statement: it never says when to call this versus the overlapping regime tools (btc_dominance, fear_greed, altcoin_season, dca_signal), nor does it state any preconditions or exclusions. An agent must infer usage entirely from the tool name and purpose.

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