Skip to main content
Glama

wait_for

Read-only

Waits for file existence, absence, or stability, port open/closed, URL success, or process exit; fails when the timeout expires.

Instructions

Wait until file_exists/file_gone/file_stable, port_open/port_closed, url_ok, process_exit; fails 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": {
      "condition": "<condition>",
      "target": "<target>"
    },
    "name": "wait_for"
  }
}

Input Schema

NameRequiredDescriptionDefault
statusNo
targetYespath, host:port, URL or PID
containsNo
stable_sNo
conditionYes
timeout_sNodefault 60
interval_msNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.2

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already mark this as read-only, so the description's main added behavior is that the call blocks until a condition is met and fails on timeout. It omits polling behavior, what failure looks like, and whether status filtering affects matching.

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. The semicolon list is compact and immediately identifies the operation and its failure mode.

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

Completeness2/5

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

For a 7-parameter blocking/polling tool with no output schema and low schema coverage, the description is too thin. It should clarify parameter semantics and basic polling/timeout behavior.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 29%, yet the description adds little parameter meaning beyond repeating the condition enum. It does not explain status, contains, stable_s, interval_ms, or the timeout default, leaving several non-obvious parameters undocumented.

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 wait-until operation and enumerates the conditions it supports, so the core purpose is clear. It does not distinguish itself from sibling utilities such as cron or http, so it stops short of a 5.

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

Usage Guidelines3/5

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

The phrase 'Wait until...' implies the use case, and 'fails on timeout' gives a boundary condition. There is no explicit when-to-use guidance, no exclusions, and no named alternatives.

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