Skip to main content
Glama

Images ready so far

get_progress

Retrieves progress for an image generation or edit key so the image card can display results as they finish. Intended for internal UI updates, not direct calls.

Instructions

Used by the image card to show images as they finish. Not useful to call directly.

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": {
      "key": "<key>"
    },
    "name": "get_progress"
  }
}

Input Schema

NameRequiredDescriptionDefault
keyYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.5/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden. It reveals only that this is UI-support plumbing consumed by an image card; it says nothing about polling semantics, whether results are cumulative or partial, cost/rate implications, or what the response contains.

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?

Two short sentences with no filler, and the critical caveat is stated directly. Nothing is padded, though the brevity comes at the cost of the missing details noted elsewhere.

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

Completeness2/5

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

For a one-parameter, annotation-free, output-schema-free tool, the definition should at minimum explain the key and what progress means. The 'do not call directly' warning reduces the practical need, but an agent that does decide to call it has almost nothing to go on.

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

Parameters1/5

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

Schema description coverage is 0% and the single required parameter 'key' is never mentioned in the description. The description does not compensate at all, so an agent has no idea whether 'key' is a job id, an image id, or a card identifier.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description says it shows images 'as they finish' for the image card, which conveys a progress/polling purpose, but it never states a specific verb-plus-resource (e.g. 'poll generation progress for a job key') or what unit of progress is returned. It does not distinguish this from get_generated_image or how progress differs from a finished image lookup.

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

Usage Guidelines3/5

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

'Not useful to call directly' is an explicit when-not-to-use statement, which is genuinely useful routing information. However, it names no alternative for an agent that actually wants image results, leaving the agent to infer get_generated_image from the sibling list rather than from this text.

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