Skip to main content
Glama

Scan Instruments

tt_scan_instruments
Read-onlyIdempotent

Which instruments are reading a given way RIGHT NOW — the scan step between looking at one chart and building a strategy.

underlyings is a comma-separated list ("NIFTY 50, NIFTY BANK, SENSEX"); empty scans every covered root whose store is configured. A name this does not read does NOT sink the call — the rest are scanned and it is named in not_instruments; only a list with nothing readable in it is refused. verdict filters to one of Strong Buy / Buy / Neutral / Sell / Strong Sell, in any case; empty returns every instrument's reading with a by_verdict breakdown.

conditions (default true) adds the wire conditions to every row. On a whole-board scan — underlyings empty — it is forced OFF, because that response ran to ~63,000 characters and clients refuse to render it; pass a short underlyings list to get the conditions back. The response says which you got, in conditions_included.

Each match carries conditions — the EXACT Tradetron wire conditions for what is currently firing on it, in the same grammar the screener and the strategy engine already use. That is the point of this tool: the reading can be saved as a screener condition or carried into a strategy without anyone retyping it. Never paraphrase those strings; offer them as they are.

ALWAYS name the timeframe when reporting — a 5m reading and a 1h reading disagree constantly, so "NIFTY is a Buy" with no timeframe is meaningless. Call out divergent rows: those are instruments where the moving averages and oscillators point opposite ways, which is the normal state of a trend rather than a contradiction.

MARKET DATA, NOT ADVICE. Do not tell anyone to buy or sell and do not present the list as "best opportunities" — it is a filter over indicator tallies. No auth required.

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

Input Schema

NameRequiredDescriptionDefault
verdictNoFilter to one of: Strong Buy, Buy, Neutral, Sell, Strong Sell. Matched case-insensitively; omit for all.
timeframeNo5m
conditionsNo
underlyingsNo
lookback_daysNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Annotations already cover safety (readOnly, idempotent, non-destructive, closed world), but the description adds substantial behavior beyond them: whole-board scans force `conditions` OFF because the response reached ~63,000 characters, unreadable names don't fail the call but land in `not_instruments`, and only an entirely unreadable list is refused. It also flags the response fields `conditions_included` and `divergent`, and states no auth is required.

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?

Purpose is front-loaded and each paragraph handles a distinct concern (targeting, conditions behavior, wire-condition fidelity, reporting rules, disclaimer). The em-dash-heavy prose is dense and the conditions paragraph covers similar ground twice, but little is outright filler.

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 output schema, the description does the work of describing returns: `by_verdict` breakdown, `not_instruments`, `conditions_included`, the `conditions` string field, and `divergent` rows. The remaining gap is that two of the five parameters (`timeframe`, `lookback_days`) are never explained, which matters for a tool whose readings are timeframe-sensitive.

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

Parameters3/5

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

Schema description coverage is only 20%, so the description must carry the load. It well explains `underlyings` (comma-separated, empty = all roots with configured stores) and `verdict` (five levels, case-insensitive, empty returns all with a `by_verdict` breakdown) and the default-plus-forced-off behavior of `conditions`, but `timeframe` and `lookback_days` get no semantic explanation in either schema or description.

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 opening states a specific verb, resource, and scope: 'Which instruments are reading a given way RIGHT NOW' plus a positional framing as 'the scan step between looking at one chart and building a strategy.' An agent can immediately tell this is a read-only indicator scan, not a screener query or a strategy builder.

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?

It gives concrete usage context (the step before building a strategy, feeding conditions into a screener or strategy) and operational rules: empty `underlyings` scans everything, pass a short list to get conditions back, name the timeframe when reporting. It does not name a specific sibling tool to use instead for adjacent jobs, so it stops short of explicit alternative routing.

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.

Resources