Skip to main content
Glama

Standby for owner (5 min)

await_owner
Read-onlyIdempotent

Hold the MCP connection open for up to 5 minutes after a task completes so the PC owner can send follow-up instructions via the ZeroIDE tray, even without chat access.

Instructions

Call at the end of a completed task (right after task_status({ status: 'done' })) to hold the MCP connection open for 5 minutes (default waitMinutes: 5) so the PC owner can send you follow-up instructions from the ZeroIDE tray even if they do not have access to the chat window. Uses 45-second keepalive pulses under the hood so cloud proxies never time out. If it returns STANDBY_KEEPALIVE, immediately call await_owner({ agent, continueStandby: true }) until either the owner sends a message (NEW_INSTRUCTION_FROM_OWNER) or the 5 minutes expire (STANDBY_TIMEOUT_COMPLETED / STANDBY_RELEASED_BY_OWNER).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "await_owner"
  }
}

Input Schema

NameRequiredDescriptionDefault
noteNoShort human-readable explanation (1 line, in the user's language) of what you are about to do and why. Shown to the user on the approval card. Always provide when calling mutating tools.
agentNoShort consistent identifier or display name of this agent (e.g. 'Claude · Лендинг', 'Тесты', 'Мой агент'). Used to separate tasks and route tray messages when multiple agents work in parallel.
summaryNoShort completion message shown to the owner in the tray chat card while waiting.
waitMinutesNoTotal standby duration in minutes (default 5).
continueStandbyNoSet true on subsequent keepalive pulses within the same 5-minute standby window.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.6/5.0
Behavior4/5

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

Goes well beyond the readOnly/idempotent annotations by disclosing the 5-minute hold, the 45-second keepalive pulses that defeat cloud proxy timeouts, and the four named return codes with the required loop behavior. It does not clarify what happens to the pending task state or what the returned instruction payload looks like, which is the one remaining gap; no output schema exists to cover it.

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?

Front-loaded with the trigger and purpose, then the mechanics, then the return-code handling — a sensible order. It is dense with backticked tokens in one long paragraph, but each sentence carries operational information; only the keepalive-proxy detail is arguably optional.

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?

For a blocking standby tool with no output schema, the description supplies the full protocol: duration, keepalive cadence, exact return tokens, and the exact continuation call. An agent can execute the entire loop correctly from this text alone.

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 baseline would be 3, but the description adds real meaning: it fixes the default waitMinutes at 5 and, more importantly, explains the continueStandby loop semantics and when continueStandby must be set true. note, summary, and agent are left to the schema, which documents them adequately.

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?

States a precise action: hold the MCP connection open for 5 minutes so the PC owner can send follow-up instructions from the tray. It is unmistakably distinct from siblings like task_status, user_message, and agent_message, and names the exact trigger point (right after task_status({status:'done'})).

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?

Gives an explicit when-to-call (end of a completed task, immediately after task_status done) and explicit follow-on routing: on STANDBY_KEEPALIVE call again with continueStandby:true, and stop on NEW_INSTRUCTION_FROM_OWNER or the two terminal codes. The alternative path (owner may lack chat access, hence the tray) is explained rather than left to inference.

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