BRS Signals

get_directional_bias

Should you be trading Bitcoin right now, and in which direction?

Returns side (bullish / bearish / WAIT) with confidence, the regime and zone the call was made in, the reason, btc_price and timestamp. WAIT is the most common answer and means no edge exists — respect it; do not force a trade. Confidence is normalised against how much evidence was reachable: sent signals typically land 0.30–0.50, so compare against the distribution, not 1.0. Signals suppressed by the noise filter are shown (suppressed=true), never hidden.

Requires a Pro API key or x402 payment. Free alternative: get_convergence.

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

TDQS

A4.6/5.0

Behavior4/5

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

With no annotations provided, the description carries the full burden. It discloses the authentication requirement (Pro API key or x402), explains the confidence normalization (0.30–0.50 range), and notes that suppressed signals are shown, not hidden. It does not explicitly mention read-only behavior or rate limits, but the given context is substantial.

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 bit longer than the minimal two-sentence ideal, but every sentence adds value: purpose, return fields, WAIT interpretation, confidence normalization, suppression behavior, and auth/alternative. It is front-loaded with the key question. Minor verbosity keeps it from a 5.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given that there are no parameters and an output schema exists, the description need not detail return types further. It provides the necessary interpretive context (WAIT meaning, confidence comparison, suppression flag) and access requirements, making it complete for an agent to decide when and how to use the tool.

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 has zero parameters, so the baseline is 4. The description adds no parameter detail (unnecessary), but the output semantics are explained well. This is appropriate for a no-input tool.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a clear, specific purpose ('Should you be trading Bitcoin right now, and in which direction?') and details the output fields (side, confidence, regime, zone, reason, price, timestamp). It distinguishes itself from the sibling get_convergence by mentioning it as a free alternative.

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

Usage Guidelines5/5

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

It explicitly names get_convergence as a free alternative, implying when to use that instead (when no Pro API key/payment). It also gives guidance on interpreting WAIT ('respect it; do not force a trade'), which helps the agent decide when to act on the result.

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

All BRS Signals tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4/5.0

Disambiguation4/5

Tools like get_convergence, get_directional_bias, and get_dashboard are related but clearly scoped: convergence checks sensor agreement, directional_bias gives the trade call, dashboard bundles everything. Mempool fees vs stats are distinct (rates vs pending tx). Some overlap exists between convergence/regime_current, but descriptions disambiguate well.

Naming Consistency5/5

All tools follow a consistent get_verb_noun pattern (get_block_tip, get_funding_divergence, get_system_health). The only exception is query_db, which uses 'query' instead of 'get', but it still follows the verb_noun structure and same snake_case style. No mixed conventions.

Tool Count4/5

15 tools is at the high end of the ideal range, but each serves a distinct function in a complex domain: sensor convergence, regime, funding, gamma, mempool, system health, audit. The Pro/free tier adds some apparent duplication (get_convergence vs get_directional_bias), but they address different questions.

Completeness5/5

The tool set covers the full workflow: convergence check, directional call, regime context, specialized indicators (funding, gamma, stablecoin flows, fee histogram), mempool data, system health, audit trail, and a queryable database. No obvious dead ends; public signal history and counters support verification.

Resources

Need Help?