Skip to main content
Glama

Load a generated image

get_generated_image

Loads a generated image by ID for display in an image card, optionally returning a resized PNG or continuing base64 output; not intended for direct calls.

Instructions

Used by the image card to load an image by id. 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": {
      "id": "<id>"
    },
    "name": "get_generated_image"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
edgeNoSend a smaller copy of a PNG, its long edge at most this many pixels, with transparency kept.
offsetNoWhere to continue from, in base64 characters.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.8/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden, and it says nothing about what the call returns, whether the image payload is chunked, or how failures behave. The presence of an 'offset' parameter in base64 characters strongly implies paginated/chunked responses, yet the description never mentions this behavior.

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, front-loaded, with no filler. The brevity is appropriate, though part of the limited space is spent discouraging use rather than describing behavior.

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 place a caller could learn how the returned image data is delivered. Given the offset-based resumption implied by the schema, the description is noticeably thin, but its blunt 'don't call this directly' warning does prevent the most likely misuse.

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 coverage is 67%, below the high-coverage baseline, so the description needs to compensate but adds nothing beyond 'by id'. The two most consequential parameters, 'edge' (downscaling) and 'offset' (resuming a base64 stream), are only explained in the schema, and their interaction with paging is never clarified.

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 gives a specific verb and resource ('load an image by id') but immediately frames it as an internal helper for the image card rather than a tool with a standalone purpose. It says nothing to distinguish it from siblings like get_layer_set or generate_image, so an agent can't tell what unique resource it returns.

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 valuable guidance. However, it names no alternative and gives no condition under which direct invocation would be acceptable, leaving the agent without a route.

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