Skip to main content
Glama

Show thumbnail progress

show_generation_progress
Read-onlyIdempotent

Show a simple loading card for an existing generation. Call once after create_generation accepts the run. The card polls read-only status and shows the resulting thumbnail gallery when ready. Do not start another generation or repeatedly open cards to check progress. No extra generation allowance.

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": {
      "runId": "<runId>"
    },
    "name": "show_generation_progress"
  }
}

Input Schema

NameRequiredDescriptionDefault
runIdYes

Output Schema

NameRequiredDescriptionDefault
modeNo
errorNo
runIdYes
configNo
statusYes
webUrlYes
optionsNo
progressNo
projectIdYes
allFlaggedNo
packagingUrlNo
pollAfterSecondsNo
artifactExpiresAtNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so safety is covered. The description adds genuinely new behavior: the card itself polls status, renders a gallery on completion, and consumes 'No extra generation allowance' — a cost side-effect an agent would not learn from annotations. It does not describe failure or timeout behavior of the polling.

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?

Four short sentences, front-loaded with the core action, then sequencing, then the behavioral constraint. Nothing is padded, though the intended-action and prohibition sentences could be merged for tighter scanning.

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?

An output schema exists so return values need no explanation, and annotations cover the safety profile; the description fills the remaining gaps around call sequencing and credit consumption. The one unresolved gap is how to obtain or validate runId, which is a real but minor omission for a one-parameter tool.

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 0% for the single runId parameter, so the description must carry the meaning. It only indirectly implies runId is the run returned by create_generation ('after create_generation accepts the run') and gives no format, length, or lookup guidance beyond that.

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 gives a specific verb and resource ('Show a simple loading card for an existing generation') and states what the card does: polls read-only status and renders a thumbnail gallery when ready. It is distinguishable from create_generation and list_generations, though it never explicitly contrasts with show_thumbnails or get_generation, which an agent might otherwise consider for viewing results.

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?

Timing is stated precisely ('Call once after create_generation accepts the run') plus explicit prohibitions ('Do not start another generation or repeatedly open cards to check progress'). It lacks a named alternative for agents that want to poll programmatically rather than render a card, which keeps it from a 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