ProteinIQ

Continue ProteinIQ Workflow Run

continue_workflow_run

Continue a paused workflow run. At a curation checkpoint, first provide the candidate set digest and approved candidate IDs returned by the workflow run curation API.

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

Input Schema

Name	Required	Description
`note`	No	Optional curation rationale recorded in run history.
`run_id`	Yes	Paused workflow run ID.
`max_credits`	No	New spending ceiling; null removes it. Omit to retain it.
`candidate_set_digest`	No	Current curation candidate-set digest. Required with approved_candidate_ids when no decision is recorded.
`approved_candidate_ids`	No	Candidate IDs approved for continuation. At least one is required by curation checkpoints.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 5, 2026

addedInput schema / properties / max_credits

Added value: +{
+  "description": "New spending ceiling; null removes it. Omit to retain it.",
+  "minimum": 0,
+  "type": [
+    "integer",
+    "null"
+  ]
+}

First observedSep 30, 2026

TDQS

A3.7/5.0

Behavior3/5

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

Annotations establish that this is a non-read-only, non-destructive, closed-world mutation, so the safety profile is partly covered. The description adds the sequencing requirement at curation checkpoints, but says nothing about what continuation does to the run, credit consumption, or reversibility. With annotations carrying part of the burden, a 3 is appropriate.

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, purpose front-loaded, no filler. Every clause contributes either the action or the checkpoint prerequisite.

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?

For a mutation with annotations but no output schema, the description covers purpose and the key curation prerequisite adequately. Minor gaps remain around what the continuation returns and the general precondition for non-curation paused runs, but nothing critical to calling it correctly is absent.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/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 goes beyond the schema by stating that candidate_set_digest and approved_candidate_ids must first be obtained from the workflow run curation API and supplied together at a curation checkpoint, clarifying a cross-parameter dependency the schema alone does not express.

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 + resource ('Continue a paused workflow run'), which distinguishes it from the read-oriented siblings like get_workflow_run and the terminal siblings cancel_workflow_run. It does not, however, explicitly contrast with retry_workflow_run or start_workflow, leaving some ambiguity about which resume path applies.

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?

The description implies usage context by naming the curation checkpoint case and telling the agent what to supply at that point. It gives no guidance on when to use this versus retry_workflow_run or start_workflow, nor on the preconditions for resuming a non-curation paused run.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All ProteinIQ 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?