Skip to main content
Glama

wait

Read-only

Pause execution for a set number of seconds before continuing, optionally targeting a specific session.

Instructions

Wait for a specified number of seconds before continuing.

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

Input Schema

NameRequiredDescriptionDefault
secondsNoHow long to wait, in seconds. Default: 2.
session_idNoSession ID to target. Optional: falls back to the MCP-server-held dev_start session, then this project's `vibeview dev --detach` state, if either is available.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

The readOnlyHint=true annotation is consistent with the description, which correctly implies a non-mutating blocking call. Beyond that, the description adds nothing: it does not say whether the wait blocks the whole session or just this call, whether there is a maximum duration, or what happens if session_id points at a non-running session — all real concerns for a delay tool with no annotations covering them.

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?

A single front-loaded sentence with no filler, no redundancy against the schema, and no trailing explanation. For a trivial sleep tool this is an efficient size, though the brevity is also where the guidance gaps come from.

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 is simple, unrequired params are defaulted, and the schema fully documents both parameters, so the description does not need to explain return values or argument formats. It is slightly thin on session targeting and blocking scope, but nothing essential to invoking it correctly 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 description coverage is 100%, and both parameters already carry clear schema text including the default of 2 seconds and the session_id fallback chain. The description mentions only 'a specified number of seconds' and does not touch session_id, so it adds essentially no meaning beyond the schema; 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 and resource ('Wait for a specified number of seconds') plus the effect ('before continuing'), so an agent can immediately tell it is a blocking delay rather than an app-interaction tool. No sibling is named, but among the listed siblings none overlaps with a plain sleep, so the risk of confusion is low.

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

Usage Guidelines2/5

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

The description gives no when-to-use condition, no prerequisites, and no guidance about how this relates to waiting on app state (siblings like get_run, logs, screenshot). An agent must infer entirely on its own when a fixed sleep is preferable to polling.

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