FILTRIX.net

resume_paper_run

Resume a paused paper run (needs a Pro plan and a healthy feed).

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": "resume_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.5/5.0

Behavior3/5

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

Annotations already declare this is a non-read-only, non-destructive, open-world, non-idempotent mutation; the description adds the plan/feed preconditions, which is useful context beyond them. It stays silent on state-transition behavior (what happens if the run isn't paused, what state it resumes to) and does not reconcile the non-idempotent annotation with the schema's idempotency_key retry guarantee.

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?

One short sentence with the verb first and the precondition in parentheses – no wasted words. It is arguably too terse for a stateful mutation, but 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, full parameter documentation, and annotations covering the safety profile, the description only needs to add preconditions and routing, and it covers the preconditions. The missing piece is what happens when the run is not in a paused state.

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 run_id, idempotency_key, and expected_version are already fully documented in the schema, including the source of the UUID and version. The description adds no meaning beyond that, making the baseline 3 correct.

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 verb and resource ('Resume a paused paper run'), which is clearly the inverse of the sibling pause_paper_run and distinct from start_paper_strategy or close_paper_run. It does not name an alternative explicitly, so it stops short of a 5.

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?

Supplies preconditions ('needs a Pro plan and a healthy feed') that determine whether the call can succeed, which is genuine usage guidance. It does not say when to prefer this over start_paper_strategy, nor what to do if the run is not currently paused, leaving the routing decision implicit.

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?