Skip to main content
Glama

get_generation_status

Read-only

Poll the status of a custom plugin preview or save job (reads from DB instantly — no blocking). Call every 10-15 seconds while status = "running". status = "interrupted" → generation paused for review, check interrupt.type for details. status = "complete" → inspect the returned payload for the plugin result. status = "error" → generation failed, check error field.

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": {
      "thread_id": "<thread_id>"
    },
    "name": "get_generation_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
thread_idYesThread ID from propose_plugin_preview or approve_plugin_preview

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Beyond the annotations, it discloses that reads are instant and non-blocking, specifies polling cadence, and explains the meaning of each status plus the fields to inspect for interrupted, complete, and error outcomes. This adds substantial behavioral context for a polling tool.

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 compact and front-loaded: it states the action first, then polling behavior, then status-handling branches. Every sentence provides actionable information with no redundant wording.

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?

For a simple read-only status-polling tool with one parameter and full schema coverage, the description covers polling cadence, status semantics, and which fields to inspect. Although no output schema exists, it sufficiently explains the relevant return states and payload checks.

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?

The input schema has 100% description coverage, including that thread_id comes from propose_plugin_preview or approve_plugin_preview. The description adds only that the job may be a preview or save job, not additional syntax or constraints, so the schema baseline of 3 applies.

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 states a specific verb and resource: 'Poll the status of a custom plugin preview or save job.' It clearly distinguishes status polling from sibling tools like propose_plugin_preview and approve_plugin_preview.

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 operational guidance: call every 10-15 seconds while status is 'running,' and branch on 'interrupted,' 'complete,' and 'error.' It does not name alternative tools or state when not to use this tool, so it falls short of a full 5.

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