Sora Commander

Overview Schema Source Related Servers Discussions Admin

stop_process

Cancel an existing JobManager session by session_id to stop a running job; confirm the exact target and do not use it to start a new session.

Instructions

Use only when the Owner explicitly intends to cancel an existing session_id. This modifies a running job; does not start a new one. Confirm the exact target; do not infer outcomes from missing sessions.

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

Input Schema

Name	Required	Description	Default
`session_id`	Yes	Opaque existing JobManager session ID; never use it to start a second job.

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.2Nov 9, 2026

TDQS

A3.6/5.0

Behavior3/5

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

No annotations are supplied, so the description carries the full burden: it does disclose that this mutates a running job and that absent sessions should not be read as an outcome. It does not say whether termination is graceful or forced, whether repeated calls are idempotent, or what error state results from an invalid/expired session_id.

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?

Three short sentences, front-loaded with the trigger condition, mutation semantics and a safety warning. 'Do not infer outcomes from missing sessions' is slightly telegraphic but saves space without obscuring intent.

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 one required parameter, full schema coverage and an output schema present, the description covers the when, the what, and the main hazard, which is sufficient to call it correctly. The remaining gap is termination/error semantics, which matters for a kill-style operation but is not strictly required to invoke it.

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 coverage is 100% and the single parameter's schema already explains that session_id is an opaque existing JobManager ID not to be reused for a new job. The description's 'confirm the exact target' adds a procedural nudge but no new meaning about the value itself, 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 verb+resource ('cancel an existing session_id') and explicitly scopes it as modifying a running job rather than starting one, which separates it from run_command/run_command_wait. It never names the obvious sibling stop_process_wait, so the differentiation is partial.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

'Use only when the Owner explicitly intends to cancel an existing session_id' gives a clear positive condition plus an exclusion ('do not infer outcomes from missing sessions'). It stops short of routing the agent to the blocking variant stop_process_wait, which is a meaningful gap for a destructive operation.

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