BRS Signals

get_gamma_exposure

Where does dealer hedging amplify or dampen the move? (Pro stream)

Net dealer gamma and the flip level that acts as a price magnet.

Returns: - dealer_net_gamma: Net dealer gamma position - gamma_flip_level: Price level where gamma flips (key support/resistance) - put_gamma, call_gamma: Put and call gamma separately - gamma_regime: Current gamma regime interpretation

Gamma flip levels act as magnetic price levels. Above flip = dealers hedge with the trend (accelerating). Below flip = dealers hedge against the trend (dampening). Large negative gamma = explosive potential.

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

TDQS

B3.4/5.0

Behavior2/5

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

No annotations are provided, so the description must carry the full burden of behavioral disclosure. It explains the output semantics and how to interpret gamma flip levels, but does not mention read-only nature, data latency, subscription requirements, or any side effects. This is a significant gap for a tool with no annotation coverage.

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 well-structured, front-loading the core concept in a question, then providing a brief summary and a clear Returns list. Every sentence adds value without being overly verbose. The format is scannable and efficient.

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?

Given that the tool has no parameters and an output schema exists, the description provides sufficient interpretive context (e.g., gamma flip as magnetic level, negative gamma meaning explosive potential). However, it omits details about data source, update frequency, or any caveats about the Pro stream, which would improve completeness.

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 for parameter semantics is 4. The description correctly focuses on outputs and interpretation, and there is no schema information to supplement. It effectively communicates that no input configuration is needed.

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 clearly explains the tool's purpose: it returns net dealer gamma, gamma flip level, and related metrics. It distinguishes from siblings by focusing specifically on gamma exposure, making it clear this is about dealer hedging dynamics. The opening question is slightly indirect, but the Returns list makes the purpose explicit.

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?

The description implies usage for assessing whether dealer hedging amplifies or dampens moves, but it does not explicitly state when to use this tool versus alternatives like get_directional_bias or get_funding_divergence. No exclusions or alternative recommendations are provided.

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?