Skip to main content
Glama
claude-proxmox-controller

claude-proxmox-controller

wait_for_request

Read-onlyIdempotent

Waits for a pending Proxmox request that returned 'waiting' until the user responds or work completes, then returns the answer or 'waiting' after about 45 seconds.

Instructions

Go on waiting for a request that came back with status 'waiting' (the user has not answered its approval window yet, or its work is still going): gives that request's answer when there is one, or 'waiting' again after about 45 seconds — then call this again. Nothing is asked of the user, and no reason is needed.

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": {
      "request": "<request>"
    },
    "name": "wait_for_request"
  }
}

Input Schema

NameRequiredDescriptionDefault
requestYesThe id the 'waiting' answer gave.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already establish read-only, idempotent, and non-destructive behavior. The description adds meaningful context beyond that: it explains the return behavior ('answer' or 'waiting' again), the approximate wait duration, and that no user interaction is needed.

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?

The single-sentence description is front-loaded with the core action and remains reasonably compact. The parenthetical and trailing reassurance about user input are useful, though slightly dense.

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?

For a polling tool with no output schema, the description adequately explains what is returned and that the caller should repeat the call. It could mention expiration or terminal states more explicitly, but it is largely complete for the tool's complexity.

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 the description does not add syntax or format details beyond identifying the request as one that came back with status 'waiting'. The schema already defines the request id sufficiently.

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 states a specific action: continue waiting on a request that previously returned status 'waiting'. It clearly communicates the polling purpose, though it does not explicitly contrast itself with any sibling tool.

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?

It tells the agent to use this only for requests that came back with 'waiting' and to call it again after roughly 45 seconds. It provides clear usage context but does not name alternatives or state when not to use the tool beyond the implied status condition.

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