Sora Commander

by kurojack-jp

Overview Schema Source Related Servers Discussions Admin

Python

Local

await_process_output

Waits on an existing JobManager session for a bounded period and returns its result without starting another job.

Instructions

Wait for an already-running JobManager session, never start another.

Use to wait on an already-started session_id for a bounded period and retrieve its result. This is observation, not a new command; do not reissue run_command on timeout.

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

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

A4.1/5.0

Behavior4/5

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

With no annotations, the description carries the behavioral burden and does so reasonably: it frames the call as pure observation, states the wait is bounded, and warns that a timeout is not a signal to re-run the command. That timeout semantics context is valuable and goes beyond the schema, though the on-timeout return state (pending ID to continue) is only spelled out in the parameter description rather than here.

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?

The core constraint is front-loaded in the first sentence. There is mild redundancy — 'Wait for an already-running JobManager session' and 'Use to wait on an already-started session_id' restate the same condition — but no filler sentences.

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 two-parameter observation tool with an output schema to describe return values, the description covers the essential risk (accidental job duplication) and the bounded-wait behavior. Without annotations, a note on permissions or concurrency behavior would round it out, but nothing critical for correct invocation is missing.

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%, so both parameters are already documented, including the wait_seconds range and timeout continuation behavior. The description reinforces that session_id must refer to an already-started job but adds no new syntax, units, or constraints beyond the schema, which is the expected baseline of 3.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource ('Wait for an already-running JobManager session') and explicitly scopes it to an existing session rather than a new command. It also names the sibling it must not be confused with ('do not reissue run_command'), so an agent can separate it from run_command/run_command_wait without reading schemas.

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?

It gives clear when-to-use guidance ('wait on an already-started session_id for a bounded period') plus an explicit when-not ('never start another', 'do not reissue run_command on timeout'). It stops short of distinguishing itself from the closely related sibling await_command_result or read_process_output, which an agent would still have to infer.

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