Skip to main content
Glama

reservation_wait

Block and poll a reservation until it allocates a place or times out, returning token state, allocations, and whether it changed.

Instructions

Block-and-poll a reservation until it allocates a place, or times out.

        ``timeout_s`` is clamped to at most 25.0 (PlaceSession.reservation_wait,
        §11.14), like ``wait_for_change``. Only an *acquired* reservation
        auto-refreshes coordinator-side -- polling here IS what keeps a
        merely-``waiting``/``allocated`` reservation's TTL alive, so the
        token still needs an ``acquire_place`` (or another ``reservation_wait``/
        ``cancel_reservation``) soon after this returns, or it expires
        ~60s after creation regardless of the outcome reported here.
        Returns ``{"token", "state", "allocations", "changed"}`` --
        ``changed`` is True iff the reservation is allocated by the time
        this returns; a dead token (expired/invalid/unknown) or a genuine
        timeout both report ``changed=False`` without raising. Non-
        destructive but not idempotent (each call keepalive-polls).
        

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tokenYes
timeout_sNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior5/5

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

The description discloses significant behavioral details beyond the annotations: timeout_s is clamped to 25.0, polling keeps TTL alive for waiting/allocated reservations, dead tokens or timeouts return changed=False without raising, and the tool is non-destructive but not idempotent. These details are consistent with the annotations (false for readOnly/idempotent/destructive) and add context.

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 dense but every sentence adds critical information: purpose, timeout clamp, TTL mechanics, return semantics, and error behavior. It is front-loaded with the purpose and uses a structured format with clear conditional clauses.

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

Completeness5/5

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

Given the tool's complexity, the description covers the purpose, usage, timing semantics, return values (including edge cases like dead tokens), and follow-up actions. The output schema exists and the description supplements it with behavioral context, making it a complete guide for an agent.

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

Parameters4/5

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

Despite 0% schema description coverage, the description explains the timeout_s parameter's clamping behavior and its implications, and the return behavior distinguishes timeouts from allocation. The token parameter is self-explanatory, so the description adds meaningful semantics for the parameters that need it.

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: 'Block-and-poll a reservation until it allocates a place, or times out.' It identifies the resource (reservation) and the action (wait/poll), distinguishing it from other reservation tools like reserve or acquire_place.

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 clear context on how to use the tool, noting the timeout clamp and the need to call acquire_place (or another reservation_wait/cancel_reservation) soon after it returns. However, it does not explicitly list alternatives or state when not to use it beyond the immediate follow-up, so it doesn't fully meet the 'explicit when/when-not/alternatives' standard.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/onurcelep/labgrid-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server