Orgo MCP Server

orgo_wait

Read-onlyIdempotent

Pause execution for a specified duration. Used for waiting for pages to load, animations to complete, or applications to start.

Instructions

Wait for a specified duration.

Useful for waiting for pages to load, animations to complete,
or applications to start.

Args:
    params (WaitInput): Input containing:
        - computer_id (str): Computer ID
        - seconds (float): How long to wait, 0.1-60 (default: 2)

Returns:
    str: Confirmation of wait completion

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": {
      "params": "<params>"
    },
    "name": "orgo_wait"
  }
}

Input Schema

Name	Required	Description	Default
`params`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jan 9, 2026

TDQS

A4/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, which fully describe the tool's safety profile. The description adds context about typical use cases but does not reveal additional behavioral traits beyond what annotations provide. There is no contradiction.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is concise and well-structured. It starts with a one-line summary, followed by usage examples, then parameter details, and finally return type. Every sentence adds value without redundancy.

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?

The tool has few parameters, good annotations, and an output schema. The description covers the return value as a confirmation string. It is complete for a simple waiting tool, though it could mention potential error conditions or timeout behavior for a perfect score.

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?

The description restates the parameters and their types (computer_id, seconds) with default and range, which mirrors the input schema. Given that schema description coverage is 0% (the schema itself includes descriptions for parameters), the tool description adds minimal new meaning. A baseline score of 3 is appropriate.

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 clearly states the tool's function: 'Wait for a specified duration.' It uses a specific verb-resource combination and is unambiguous. Among sibling tools, waiting is a unique action, so it is easily distinguishable.

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?

The description provides explicit usage guidance: 'Useful for waiting for pages to load, animations to complete, or applications to start.' This tells the agent when to use the tool. However, it does not explicitly state when not to use it or mention alternatives, which is acceptable given the tool's simplicity.

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