FILTRIX.net

pause_paper_run

Pause a paper run: no new entries; open positions keep their exits.

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": "pause_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 declare the mutation profile (readOnlyHint=false, destructiveHint=false), and the description adds genuinely new behavioral context: no new entries are created while open positions retain their exits. That is the key non-obvious consequence an agent needs. It does not discuss version-conflict refusal or idempotency, which the schema covers instead.

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?

A single sentence, front-loaded with the action and followed by the two operative consequences. Every clause earns its place with no redundant restatement of the tool name.

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?

The tool is simple with one required parameter, full schema coverage, annotations, and an output schema, so the description need not explain return values. It covers the essential question of what pause does to existing state; only the precondition that the run be pausable is unstated.

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?

With 100% schema description coverage, run_id, idempotency_key, and expected_version are all fully documented in the schema, including the concurrency-refusal behavior. 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?

The description gives a specific verb and resource ('Pause a paper run') and immediately defines what pausing means in domain terms. It implicitly distinguishes itself from resume_paper_run and close_paper_run by clarifying that positions stay open rather than being liquidated, though it does not name the siblings explicitly.

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 only implied: the agent can infer this is the tool for temporarily halting entries without closing positions, and that resume_paper_run is the inverse. There is no explicit statement of when to prefer pause over close_paper_run or what preconditions (e.g., run must be active) apply.

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?