Sora Commander

Overview Schema Source Related Servers Discussions Admin

stop_process_wait

Cancel an existing job by session ID, then wait a bounded time (0–90 seconds) for that same job to reach completion without starting a replay.

Instructions

Explicitly cancel a job, then observe that SAME job to completion.

Use for explicit cancellation of the existing session_id followed by a bounded wait for its observed result. No new job or automatic replay. Only cancel when Owner intended.

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": {
      "session_id": "<session_id>"
    },
    "name": "stop_process_wait"
  }
}

Input Schema

Name	Required	Description	Default
`session_id`	Yes	Opaque existing JobManager session ID; never use it to start a second job.
`wait_seconds`	No	Bounded observation time in seconds, 0 to 90 (default 50); continue existing pending ID after timeout.

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.2Nov 9, 2026

TDQS

A3.5/5.0

Behavior3/5

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

With no annotations, the description must carry the full behavioral load. It does disclose that this is a destructive cancel, that no replay or new job is spawned, and that a bounded wait follows, but it says nothing about what happens on timeout, whether the cancel can fail or partially succeed, or required permissions.

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?

Short and front-loaded, with the core action in the very first sentence. The second sentence largely restates the first ('explicit cancellation of the existing session_id followed by a bounded wait'), and 'Only cancel when Owner intended' is grammatically awkward, costing it a point.

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?

Two well-documented parameters and an output schema mean the agent has most of what it needs; the description supplies the mutation semantics and the no-replay guarantee. The remaining gap is timeout/failure behavior, which the schema only partially implies.

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 both session_id and wait_seconds (including the 0-90 bound and timeout continuation) are already documented. The description reinforces 'existing session_id' and the bounded nature of the wait, but adds no format or edge-case detail beyond the schema, so 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?

States a specific compound action: cancel an existing job and then observe that same job to completion. The emphasis on 'SAME job' and 'No new job or automatic replay' separates it from a plain cancel (stop_process) and from a start-and-wait tool, though no sibling is named 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?

'Use for explicit cancellation of the existing session_id followed by a bounded wait' gives a usable condition, and 'Only cancel when Owner intended' adds a caution. But it never names the alternatives (stop_process, await_command_result) or states when to prefer them, so routing is implied rather than explicit.

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