APEX Runner Crypto Signals

regime_confluence

$0.007 — Call this before committing to a trend or range strategy, so you don't trade a regime only one coin is in — checks whether BTC, ETH and SOL agree (confluence 1-3, WEAK/MODERATE/STRONG) and returns the dominant regime, the strongest pair, and a recommended action with Fear & Greed context.

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

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 11, 2026

TDQS

A4/5.0

Behavior4/5

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

No annotations are provided, so the description carries the full disclosure burden, and it does substantial work: it reveals the cost ($0.007), the computation (cross-asset agreement across three named assets), the output scale (1-3, WEAK/MODERATE/STRONG), and the returned artifacts including Fear & Greed context. It stops short of stating that it is strictly read-only/non-executing or whether results are cached, which leaves a small residual gap.

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?

A single sentence, front-loaded with price and the imperative 'Call this before...', then the mechanism, then the returns. It is dense but every clause carries information; the em-dash chaining makes it slightly harder to scan than a two-sentence split would be.

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?

With no input parameters, no output schema, and no annotations, the description is the only carrier of information and it covers cost, trigger condition, method, and return shape. The one omission is the set of possible regime labels returned as 'the dominant regime', which an agent must infer from the 'trend or range' phrasing.

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; baseline for a no-param tool is 4. The description correctly implies no inputs are needed by specifying the fixed asset set (BTC, ETH, SOL) internally.

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 action and scope: it 'checks whether BTC, ETH and SOL agree' and returns a confluence score (1-3, WEAK/MODERATE/STRONG), dominant regime, strongest pair, and recommended action. The phrase 'so you don't trade a regime only one coin is in' implicitly separates it from the single-asset `regime` sibling, but that sibling is never named, so differentiation is inferred rather than explicit.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

'Call this before committing to a trend or range strategy' gives a clear triggering condition tied to a concrete decision point. There are no explicit exclusions or named alternatives (e.g., when to use `regime` or `regime_micro` instead), so guidance is strong on when-to-use but silent on when-not-to.

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?