FILTRIX.net

close_paper_run

DestructiveIdempotent

Close a paper run and its open positions at the market. Confirm with the user first.

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

Input Schema

Name	Required	Description
`run_id`	Yes	Id (UUID) of one of the caller's paper runs, from get_paper_account.
`idempotency_key`	No	Optional key that makes a retry safe: the same key replays the first answer instead of acting twice. Derived from the other arguments when omitted.
`expected_version`	No	Paper account version from get_paper_account; the command is refused if the account changed since. Fetched for you when omitted.

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 9, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already declare destructiveHint=true, idempotentHint=true and openWorldHint=true, so the safety profile is partly covered. The description still adds value beyond them by disclosing that open positions are liquidated "at the market" (i.e. executed as market orders) and that user confirmation is expected before the destructive action runs.

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 short sentences with the action and its scope front-loaded, followed immediately by the confirmation requirement. No filler, no repetition of schema or annotation content.

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 rich annotations, full schema coverage, and an output schema present, the description only needs to convey the destructive scope and the confirmation step, which it does. It stops short of covering edge cases such as what happens if the run is paused or partially filled, but those are minor relative to what structured fields already supply.

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% and each parameter (run_id, idempotency_key, expected_version) is documented with sourcing and failure behavior in the schema itself. The description adds no parameter-level meaning, so the baseline of 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?

Names a specific verb and resource ("Close a paper run and its open positions") and adds the execution venue ("at the market"), which is more than a restatement of the name. It does not explicitly contrast with close_all_paper_positions or delete_run, so sibling differentiation is left implicit.

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?

"Confirm with the user first" gives a real precondition for invoking the tool, which is useful guidance. However, there is no guidance on when to prefer this over close_all_paper_positions, pause_paper_run, or delete_run, so the choice among siblings must be inferred from their names alone.

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?