FILTRIX.net

screen_events

Read-onlyIdempotent

List historical events (date, symbol, company, price, gap %, dollar volume, float, relative volume) that match the filters, newest first, with the total count. limit max 200. Pass fields=[raw column names] (max 20) to also get those values per event. Use to show concrete examples; use run_backtest for statistics.

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": {
      "filters": "<filters>"
    },
    "name": "screen_events"
  }
}

Input Schema

Name	Required	Description
`limit`	No	Events per page, 1..200.
`fields`	No	Extra raw column names (from search_filters) to return per event, max 20.
`offset`	No	Number of events to skip, for paging.
`filters`	Yes	Conditions that must all hold (AND-joined, max 20). Column names come from search_filters.

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 9, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive, open-world behavior, so the description only needs to add operational detail — and it does: newest-first ordering, a hard cap of 200 on limit, and a cap of 20 extra fields. It doesn't discuss paging semantics with offset beyond what the schema states, which keeps it just under a 5.

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 purpose and return shape, and every sentence carries information; the parenthetical field list is long but useful. The cap and routing notes are appended compactly without padding.

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 annotations covering safety and an output schema covering return values, the description only needs purpose, caps, and routing — all present. An agent has enough to call it correctly without opening sibling tools.

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 100%, so the schema already documents limit (1..200), fields (max 20), offset, and the Filter object. The description largely restates those caps and the fields format, adding little meaning beyond the structured fields, which sets the baseline at 3.

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?

States a specific verb and resource (list historical events) plus the exact fields returned, the sort order (newest first), and the total count. It also names run_backtest as the contrasting tool, so an agent can distinguish this example-listing tool from the statistics path.

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?

'Use to show concrete examples; use run_backtest for statistics' gives a clear when-to-use plus one explicit alternative. It does not address the closest sibling, screen_tickers, nor any when-not conditions, so it falls short of the full routing guidance a 5 requires.

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?