Skip to main content
Glama

ExducerAI GPU cloud

Wait for a deployment

wait_for_deployment
Read-onlyIdempotent

Poll a deployment until it reaches a state (default running) or a final state, for at most 50 seconds per call. Returns reached, the current state and whether it is final. While reached is false and final is false, call again; a live request can stay requested until staff place it, so after a few minutes tell the user and check back later instead of looping.

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": {
      "id": "<id>"
    },
    "name": "wait_for_deployment"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe deployment id (rnt_… on a live key, snd_… in the sandbox).
untilNoThe state to wait for.running
timeout_secondsNoHow long to wait in this call.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already establish read-only, idempotent, non-destructive, closed-world behavior, so the description only needs to add operational color — and it does, with the per-call 50-second ceiling and the non-obvious caveat that a live request can sit in 'requested' until staff place it. It also discloses the return fields, which matters because no output schema exists. Minor deduction for restating the 50-second maximum already encoded in the schema.

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?

Three sentences, front-loaded with the action and its time bound, then the return shape, then the retry policy. Every sentence carries distinct information — no restatement of the title and no filler.

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?

With no output schema, the description must describe what comes back, and it does precisely: reached, the current state, and whether that state is final. Combined with the polling cadence guidance, an agent has everything needed to drive the tool correctly in a loop.

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 all three parameters are documented inline, including the enum states and the timeout bounds, so the schema carries the parameter burden. The description only echoes the default target state ('default running') and adds no format or interaction detail beyond that, making the baseline 3 appropriate.

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 opens with a specific verb and resource — 'Poll a deployment until it reaches a state (default running) or a final state' — and immediately bounds the operation ('for at most 50 seconds per call'). That framing distinguishes it from a one-shot read like get_deployment or a mutation like extend_deployment without needing to name them.

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 gives explicit call-again logic ('While reached is false and final is false, call again') and a clear when-not-to-loop rule ('after a few minutes tell the user and check back later instead of looping'). The only gap is that no alternative sibling (e.g. get_deployment for a single check) is named, so the agent must infer that routing itself.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources