Skip to main content
Glama

Get Character Image

get_character_image
Read-onlyIdempotent

[read] State of a picture made by create_character_image / create_character_thumbnail / create_replace_image / create_promo_image (found by image_id or image_uuid): track (QUEUED | PROCESS | DONE | FAILED | CANCELED), error, and when DONE the image_render_url of the finished picture with its size and format.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_character_image"
  }
}

Input Schema

NameRequiredDescriptionDefault
image_idNo
image_uuidNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint/idempotentHint/non-destructive, so the safety profile is covered. The description adds real value beyond that: it discloses the state machine (QUEUED | PROCESS | DONE | FAILED | CANCELED), the error field, and that image_render_url with size and format only appear once DONE — exactly the behavioral context an agent needs to interpret a response.

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?

A single front-loaded sentence that leads with the [read] tag and the core purpose before enumerating producers and return fields. Dense but every clause carries information; only the producer list is slightly verbose.

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?

With no output schema, the description carries the return-value burden and does so well (track enum, error, render URL plus size/format). The remaining gaps are identifier-selection rules and the relationship to wait_character_image, which are minor for a status-read 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 coverage is 0% for both parameters, so the description must compensate. It does partially by naming image_id and image_uuid and framing them as alternative lookup keys ('found by X or Y'), implying they are alternates rather than jointly required. It does not say which to prefer, whether one is mandatory, or what happens if both are omitted.

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?

States a specific verb+resource (get the state of a character image) and explicitly names the four producer tools whose output it inspects, so an agent knows exactly which artifacts this applies to. It stops short of distinguishing itself from the closely related wait_character_image / cancel_character_image siblings in the same family.

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?

Usage is implied by 'State of a picture made by create_...' — poll this after kicking off a render. However, there is no explicit when-to-use vs when-not, and no guidance on choosing this over wait_character_image (which presumably blocks) or get_character_queue.

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.