Skip to main content
Glama
Sign In

Blaze

by ai.blaze.app
OverviewDiscussionsAdmin

Get generated image

get_generated_image
Read-onlyIdempotent

Get the status of an image started with generate_image, by request id. While it is running, returns the status; generation usually takes 1-5 minutes, so wait 15-30 seconds between calls. When it has finished, returns the image URL and an inline preview. If it failed, returns the reason. Read-only.

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

Input Schema

NameRequiredDescriptionDefault
idYesThe request id returned by generate_image.
workspace_keyYesKey of the workspace to act in. Call list_workspaces to see the workspaces you have access to and their keys.

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?

Annotations already cover safety (readOnly, idempotent, non-destructive), but the description adds the essential async behavior: the operation is long-running, polling is expected, and the response shape differs by state (status while running, URL plus inline preview on success, failure reason otherwise). That is exactly the context an agent needs and cannot get from annotations.

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?

Four short sentences, front-loaded with the core verb and resource, then timing, then return shapes. Every sentence carries actionable information — even the trailing 'Read-only' is at worst redundant with annotations.

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 carries the return-value burden and does so for all three terminal states (running, succeeded, failed). Parameters are fully covered by the schema, and the polling interval guidance closes the remaining gap for an async status 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 100%, so both parameters are already documented in-schema, including the list_workspaces pointer for workspace_key. The description reinforces that 'id' comes from generate_image but adds no format or edge-case detail beyond that; baseline 3 applies when the schema does the heavy lifting.

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 ('Get the status of an image') plus the scoping key ('by request id') and names the producing tool, generate_image. An agent can distinguish this from generate_image and get_generated_post 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 Guidelines4/5

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

Clearly says this is the follow-up call for a generate_image request and prescribes polling cadence ('wait 15-30 seconds between calls', 1-5 minutes typical). It does not state when-not to use it (e.g., how to cancel or what to do after terminal success), so it stops short of full when/when-not/alternatives coverage.

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

All Blaze toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources