FILTRIX.net

list_paper_records

Read-onlyIdempotent

A page of the caller's paper strategies, orders, positions, trades, events (journal) or epochs. Pass the returned cursor as after for the next page; limit max 100.

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": {
      "kind": "<kind>"
    },
    "name": "list_paper_records"
  }
}

Input Schema

Name	Required	Description
`kind`	Yes	Which records: strategies, orders, positions, trades, events (the journal) or epochs.
`after`	No	Cursor returned with the previous page; omit for the first page.
`limit`	No	Records per page, max 100.
`run_id`	No	Only records of this paper run (UUID, from get_paper_account).
`epoch_id`	No	Only records of this epoch (see kind='epochs'; reset_paper_account starts a new one).

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 9, 2026

TDQS

A3.5/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint, so the safety profile is covered. The description usefully adds cursor-based pagination and the 100-record cap, but says nothing about ordering, whether run_id/epoch_id filters compose, or what an empty page means.

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?

Two compact sentences, front-loaded with the resource scope and followed by the pagination rule; nothing is padded. The kind enumeration mildly duplicates the schema enum, but it earns its place by making the tool's breadth legible at a glance.

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 need not be explained, and the description covers scope plus paging. What remains unstated — result ordering and filter interaction — is modest for a read-only list tool whose parameters are fully documented in the schema.

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 all five parameters are already documented in the schema, including the kind enum, cursor semantics, limit bound, and the run_id/epoch_id provenance hints. The description only restates the cursor and limit behavior, adding no meaning beyond the structured fields; baseline 3 applies.

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 resource precisely by enumerating the six record kinds (strategies, orders, positions, trades, events/journal, epochs) and scopes results to 'the caller's' records. It is a clear listing tool, though it offers no explicit contrast with siblings such as list_runs or get_paper_status that also surface paper-run data.

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 guidance is limited to pagination mechanics: pass the returned cursor as `after` and keep limit under 100. There is no statement of when to choose this tool over get_paper_account, list_runs, or get_paper_status, so variant selection is left to inference.

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?