FILTRIX.net

get_run

Read-onlyIdempotent

One saved run: its filters, outcome, summary statistics and share link. With rows_limit > 0 (max 500) also returns a page of its events with their outcome values under "rows" (total, rows); that is a second API call.

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": {
      "run_id": "<run_id>"
    },
    "name": "get_run"
  }
}

Input Schema

Name	Required	Description
`run_id`	Yes	Id of one of the caller's saved runs (from list_runs or save_run).
`rows_limit`	No	Also return this many of the run's events with their outcome values (0 = none, max 500).
`rows_offset`	No	Number of events to skip when rows_limit > 0, for paging.

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 9, 2026

TDQS

A3.9/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 behavior. The description adds useful context beyond that: the response includes filters, outcome, summary stats, and share link, and rows_limit > 0 triggers a second API call returning event rows.

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?

Two front-loaded sentences with no wasted wording. The primary return content is stated first, followed by the conditional rows behavior.

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?

Given the read-only annotations, full schema descriptions, and an output schema, the definition is complete enough for an agent to call it correctly. It also explains the optional rows path and the second API call, which is the main behavioral nuance.

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%, so the baseline is 3. The description reinforces rows_limit behavior and the max 500 limit, but mostly repeats what the schema already documents and does not add syntax or validation details beyond that.

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?

States a specific resource and scope: "One saved run" with filters, outcome, summary statistics, and share link. This distinguishes it from list-style siblings, but it does not explicitly name an alternative such as list_runs.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied by the single-run framing and by the rows_limit > 0 condition for fetching events. There is no explicit when-to-use/when-not guidance or comparison to list_runs, save_run, or share_run.

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?