Skip to main content
Glama

oc_wait

Waits for or checks the status of a dispatched task by runId, up to timeout_seconds, and returns the reply, voice metadata, or current run state.

Instructions

按 runId 继续等待或查询已下发的任务,最多 timeout_seconds(0=只查状态不等待,默认 0)。刚下发还没结果、或用户问“怎么样了”时用。done 时返回本轮 reply 与 voice 元数据,按 voice.speak 播报或做 1–3 句总结;running 表示还在跑,只播报状态和已用时间,不要翻历史、不要猜进度,可以再调本工具;aborted/error 看 stopReason 和 error,并说清结果与下一步。任务已经结束后再调仍然能取到本轮回复。replyUnavailable=true 只是没读到回复,可改用 oc_last 查看。任何时候都不要因为本工具重复下发任务。

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": {
      "runId": "<runId>"
    },
    "name": "oc_wait"
  }
}

Input Schema

NameRequiredDescriptionDefault
runIdYes任务 runId(来自 oc_run 或 oc_wait 的返回)。
timeout_secondsNo等待秒数,0 表示立即返回。

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.6/5.0
Behavior5/5

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

With no annotations, the description carries the full behavioral burden and does so: it defines the timeout semantics, enumerates every terminal and non-terminal status (done/running/aborted/error), explains what stopReason, error, and replyUnavailable mean, states that calling after completion still returns the round's reply, and forbids progress-guessing or history-digging. This is far beyond what annotations would have supplied.

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?

Purpose and the timeout rule are front-loaded, followed by per-status handling, which is a sensible order for an agent reading top-down. Every clause is substantive, though the playback/summarization instructions are dense enough that the sentence runs long.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema and no annotations, so the description must describe return values, and it does: the round's reply with voice metadata, the status values, stopReason/error for failures, and the replyUnavailable flag with its fallback. Nothing an agent needs to interpret a response 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% and both parameters are already documented there, including the default of 0 for timeout_seconds. The description restates '最多 timeout_seconds(0=只查状态不等待,默认 0)' with the useful nuance of 'at most', but adds no syntax or format detail the schema lacks, so the baseline 3 applies.

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 opening clause gives a specific verb and resource ('按 runId 继续等待或查询已下发的任务') and ties it to runId, which distinguishes it from oc_run (which produces runIds) and oc_last (the fallback named later). An agent can tell what this tool is for without opening the schema.

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

Usage Guidelines5/5

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

It names the triggering situations explicitly ('刚下发还没结果' and the user asking '怎么样了'), supplies the alternative for the reply-missing case (oc_last), and closes with a hard exclusion: never re-dispatch a task through this tool. When-to-use, when-to-switch, and when-not-to-use are all present.

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

Deploy Server

Other Tools