FILTRIX.net

get_scanner_chart

Read-onlyIdempotent

Today's minute bars and recent daily bars of one symbol from the live scanner universe.

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

Input Schema

Name	Required	Description	Default
`symbol`	Yes	Ticker symbol, e.g. AAPL (case does not matter).

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 9, 2026

TDQS

B3.2/5.0

Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and open-world behavior, so safety is covered. The description adds that data comes from the live scanner universe and mixes intraday with daily bars, but omits how many daily bars are returned, whether minute bars are real-time or delayed, and how intraday sessions are bounded.

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?

A single front-loaded sentence with no filler, and the payload is stated before any qualification. It is slightly terse to the point of leaving 'recent' undefined, but nothing is wasted.

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?

An output schema exists, so return shape needn't be explained, and annotations cover the safety profile. What remains missing is the meaning of 'recent' (bar count or lookback window) and whether the scanner-universe membership is enforced, which are modest gaps for a one-parameter read tool.

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 coverage is 100% and the single symbol parameter is documented with an example and case-insensitivity note. The description contributes only the implicit constraint that the symbol belongs to the scanner universe, which is a marginal addition over 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?

The description names the concrete payload: today's minute bars plus recent daily bars for a single symbol, which is more specific than a bare verb+resource. It does not explicitly contrast with the sibling get_daily_bars, so an agent must infer the difference between this and the range-based daily-bar tool.

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?

There is no when-to-use guidance, no mention of alternatives such as get_daily_bars or get_ticker_overview, and no stated prerequisites. The phrase 'from the live scanner universe' hints at a precondition but never says the symbol must be a scanner member or what happens if it isn't.

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

All FILTRIX.net tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?