Skip to main content
Glama
linux-computer-use-mcp

linux-computer-use-mcp

by dhakseshr

wait

Pause automation until a page or app finishes loading, returning as soon as the screen settles; the seconds setting only caps the maximum delay.

Instructions

Wait for a page/app to finish loading. With until_settled (default) this returns as soon as the screen stops changing, using seconds (max 30) only as the upper limit.

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
secondsNo
screenshotNo
until_settledNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

B3.4/5.0
Behavior3/5

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

No annotations exist, so the description carries the full load. It usefully discloses the settlement heuristic and the 30-second cap, but says nothing about what happens when until_settled is false, whether a screenshot is returned by default (screenshot defaults to true), or what the response contains.

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?

Two sentences, front-loaded with the core behavior and no filler. The parenthetical fallback clause is slightly dense but earns its space by qualifying the default.

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

Completeness3/5

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

For a simple three-parameter, no-output-schema tool this is close to sufficient, but an agent still cannot tell what a call returns (screenshot image? status text?) or how the screenshot flag affects the result.

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 0%, so the description must compensate. It does so well for `seconds` (upper limit only, max 30) and `until_settled` (default, behavior), but `screenshot` — which defaults to true and likely changes the return payload — is never mentioned, leaving one of three parameters undocumented everywhere.

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?

The description opens with a specific verb and resource: 'Wait for a page/app to finish loading.' That is unambiguous and clearly distinct from siblings like click or screenshot, though it never explicitly contrasts itself with them.

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?

It explains the default mode (until_settled) and that `seconds` is only an upper bound capped at 30, which implies when the tool is cheap versus blocking. It never says when to use this versus taking a screenshot or polling with other tools, so guidance is implied rather than explicit.

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