FILTRIX.net

search_filters

Read-onlyIdempotent

Find filter columns by keyword (e.g. "gap", "float", "rsi", "earnings"). Returns the raw column name to use in filters, Trade-Ideas code, display name, description, allowed operators and value_type, best match first. Use before run_backtest or screen_events whenever you are not sure of a column name. No API key needed, free.

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

Input Schema

Name	Required	Description
`limit`	No	Maximum number of columns to return, best match first.
`query`	No	Keyword to match in column names and descriptions, e.g. 'gap' or 'float'; omit to list all.
`value_type`	No	Only columns of this type: number, string, date, time or enum.

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 9, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already cover readOnly, idempotent, openWorld and non-destructive, so the safety profile is known. The description adds genuinely new behavioral context: the exact payload returned (raw column name, Trade-Ideas code, display name, description, allowed operators, value_type) and the 'best match first' ranking, plus 'No API key needed, free.'

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

Conciseness5/5

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

Three compact sentences, front-loaded with purpose and followed by return shape and usage trigger. Every sentence carries information the agent needs; nothing is padding.

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 an output schema present and 100% parameter coverage, the definition covers purpose, return shape, prerequisites ('no API key') and placement in the workflow. The only missing piece is disambiguation from list_filters and search_scanner_columns.

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 query, limit and value_type thoroughly. The description adds only keyword examples ('gap', 'float', 'rsi', 'earnings') and reinforces best-match ordering, which is marginal value over the structured fields.

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 opens with a specific verb+resource ('Find filter columns by keyword') and gives concrete keyword examples, so the agent knows exactly what the tool does. It does not, however, distinguish itself from the sibling list_filters or search_scanner_columns, which an agent could reasonably confuse with this one.

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?

Explicit placement guidance is given: 'Use before run_backtest or screen_events whenever you are not sure of a column name,' which tells the agent both the trigger condition and the downstream tools it feeds. There is no negative guidance (e.g. when to use list_filters instead), so it falls short of a 5.

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?