Skip to main content
Glama

Smart Money Analysis

smart_money_analysis
Read-only

Banker/hot-money proxy read for one symbol from price+volume history.

Three independent families, computed from Yahoo Finance OHLCV:
  - mcdx_style: RSI-horizon decomposition (banker RSI50 / hot-money RSI40
    / retail RSI14, each scaled 0-20) — sustained slow-horizon strength
    that fast horizons can't fake reads as institutional accumulation.
  - banker_fund_oscillator: EMA(13)-smoothed 34-bar stochastic of the
    weighted typical price, 0-100, with BANKER_ENTRY/EXIT states.
  - volume_flow_composite: CMF(20) + MFI(14) + OBV trend + up/down volume
    balance → 0-100 accumulation score.
Plus a consensus vote across the three.

These are documented, reproducible formula variants inspired by the
public "banker fund" indicator family — NOT actual institutional-flow
data, and not copies of any closed-source script.

Args:
    symbol: Bare ticker — EGX: "COMI", "TMGH"; US: "AAPL"; crypto pairs
        work via Yahoo notation ("BTC-USD").
    exchange: EGX (maps to Yahoo .CA), BIST (.IS), TADAWUL (.SR); anything
        else passes the symbol to Yahoo unchanged, except spot metals
        (XAUUSD on OANDA → gold futures GC=F; the result's `note` says so).
    period: 1mo | 3mo | 6mo | 1y | 2y (default 6mo)
    interval: 1d (default) or 1h

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "symbol": "<symbol>"
    },
    "name": "smart_money_analysis"
  }
}

Input Schema

NameRequiredDescriptionDefault
periodNo6mo
symbolYes
exchangeNoEGX
intervalNo1d

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Annotations already establish read-only, non-destructive, open-world behavior, and the description goes well beyond them: it names the data source (Yahoo OHLCV), discloses exchange-to-suffix mapping and the XAUUSD-to-GC=F substitution with a returned `note`, and explicitly disclaims that these are reproducible formula variants rather than real institutional flow. That is exactly the kind of expectation-setting an agent needs before trusting 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?

Front-loaded with a one-line summary, then structured into families and an Args block, so it is easy to scan. It is dense and the per-family formula detail is more than strictly needed to invoke the tool, but that detail earns its place for interpreting the three output scales and the consensus vote.

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?

With no output schema, the description compensates by naming all three return families, their numeric scales (0-20 sub-horizons, 0-100 oscillators, BANKER_ENTRY/EXIT states) and the consensus vote. Combined with the documented data source, exchange caveats, and parameter defaults, an agent has everything needed to call and read the result.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must carry the full burden, and it does: `symbol` is defined as a bare ticker with EGX/US/crypto examples, `exchange` documents its Yahoo suffix mapping and the metals fallback, `period` enumerates the accepted values with its default, and `interval` gives the 1d/1h options. Every parameter gains meaning not present in the schema.

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?

Opens with a specific verb-and-resource statement: a banker/hot-money proxy read for ONE symbol from price+volume history, and then enumerates the three computed families. The 'for one symbol' scoping implicitly separates it from the scanner sibling, but no sibling is named, so the differentiation is not explicit.

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 explains what is computed but never says when to reach for this tool instead of egx_smart_money_scanner, multi_timeframe_analysis, or volume_confirmation_analysis. There are no exclusions or prerequisites stated; the only guidance-adjacent content is the caveat that the outputs are proxy formulas, which shapes interpretation rather than tool selection.

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.