BRS Signals

get_stablecoin_flows

Whale buying or selling intent before it reaches exchanges (Pro).

Large USDT (Tron) and USDC (Solana) movements: inflow surges precede buying pressure, outflow surges precede distribution.

Returns: - flow_regime: NORMAL, INFLOW_SURGE (buying pressure), OUTFLOW_SURGE (selling pressure) - total_net: Net stablecoin flow (positive = accumulating, negative = distributing) - Recent significant transfers over $1M

Whale stablecoin flows detect buying/selling intent BEFORE it reaches exchanges. Large USDT inflows to exchange wallets = imminent buying pressure. Large USDT outflows from exchange wallets = whales cashing out.

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

TDQS

A4.2/5.0

Behavior4/5

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

With no annotations, the description carries the burden of disclosing behavior. It details the return fields (flow_regime, total_net, transfers) and explains their meaning, providing good transparency. It does not mention rate limits or authentication, but for a read-only indicator tool this is sufficient.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is somewhat repetitive—the final paragraph restates the first paragraph's point about inflow/outflow pressure. While the 'Returns' list provides structure, the duplication makes it less concise than ideal.

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 no-parameter tool with an output schema, the description is fairly complete: it explains what the tool returns and how to interpret the signs. It lacks detail on time ranges or data sources, but these are not critical for basic usage.

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, and the input schema is empty (coverage 100%). Per the baseline for 0 params, a score of 4 is appropriate; there is no parameter semantics to add.

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 clearly states the tool detects whale buying/selling intent via stablecoin flows, with a specific verb ('detect') and resource ('stablecoin flows'). It distinguishes itself from sibling tools by focusing on pre-exchange flow analysis and specifying USDT/USDC movements.

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?

The description provides clear context on when to use the tool (to monitor buying/selling pressure before it hits exchanges) and explains the interpretation of inflow/outflow surges. However, it does not explicitly mention exclusions or alternatives, which prevents a 5.

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?