Skip to main content
Glama

wait_for_prompt

Poll a prompt generation row until it transitions to completed or failed, or until the timeout. The companion to get_generated_prompt — call this if the first call returned status: pending.

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": {
      "generation_id": "<generation_id>"
    },
    "name": "wait_for_prompt"
  }
}

Input Schema

NameRequiredDescriptionDefault
generation_idYes
timeout_secondsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose the polling/blocking nature and the two terminal states. It does not say what happens when the timeout elapses (error vs. a still-pending return), what the polling cadence is, or whether the call blocks the agent, which are the behaviors an agent most needs here.

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?

Two short sentences, behavior first and the sibling routing second; no filler or restatement of the tool name. Every clause carries information the agent needs to decide whether to call it.

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?

There is no output schema and no annotations, so the description is the only source of truth, and it omits the return shape and the post-timeout outcome. What it does cover — the polling purpose and the pending-status trigger — is the essential part, making it adequate but not complete for a blocking tool.

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 0%, so the description must compensate for both parameters and largely does not. 'generation_id' is never described (what it identifies, where it comes from), and 'timeout_seconds' appears only obliquely as 'the timeout' with no units, default, or guidance on choosing a value.

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?

States a specific verb and resource ('Poll a prompt generation row') plus the exact terminal conditions ('transitions to completed or failed, or until the timeout'). It also positions itself relative to the sibling get_generated_prompt, so an agent can distinguish the two without opening either schema.

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

Usage Guidelines5/5

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

Gives an explicit trigger: 'call this if the first call returned status: pending', which names both the alternative (get_generated_prompt) and the condition that selects this tool. The routing decision is fully resolved by the description.

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