Skip to main content
Glama

maginary-mcp

by io.github.maginaryai
OverviewDiscussionsAdmin

Get generation

get_generation
Read-onlyIdempotent

Fetch a generation by UUID (GET /api/gens/{uuid}/).

Args:
    uuid: The UUID returned by ``generate``.

Returns:
    The full generation record. If terminal, ``image_urls[]`` holds the
    finished outputs and ``processing_result.slots[]`` the per-slot detail.
    NOTE: a generation that failed server-side is a SUCCESSFUL tool call
    returning ``processing_state: "failed"`` — always check the state,
    never infer success from the absence of a tool error.

    **Follow-up actions:** A completed generation's
    ``processing_result.available_actions`` maps slot indices to valid
    action types. E.g. ``{"0": ["upscale_2x", "vary_strong", ...],
    "global": ["reroll"]}``. Use ``execute_action`` with the ``uuid``,
    a chosen ``action_type``, and the ``parent_image_index`` (the slot
    key as an int) to run an action.

    Hosted: a key obtained mid-session may be passed as
    ``_meta["maginary/api_key"]``.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
uuidYesGeneration UUID from generate or execute_action.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Beyond the readOnlyHint and idempotentHint annotations, the description reveals a critical failure-mode behavior: a server-side failed generation is still a successful tool call returning processing_state 'failed'. It also documents terminal return structure and available_actions, adding substantial interpretive context the annotations do not provide.

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?

The description is front-loaded with the purpose and uses clear labeled sections (Args, Returns, NOTE, Follow-up actions). It is longer than minimal but each section contributes meaningful operational guidance; only the hosted _meta note feels slightly tangential.

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?

For a one-parameter fetch tool with an output schema, the description covers how to interpret terminal vs failed states, what fields to inspect, and how to proceed with available actions. Nothing an agent needs to call it correctly or interpret its result is missing.

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%, and the schema already explains uuid as 'Generation UUID from generate or execute_action.' The description only restates that the UUID is returned by generate, adding little beyond what the schema provides.

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?

Description opens with 'Fetch a generation by UUID (GET /api/gens/{uuid}/)', giving a specific verb, resource, and endpoint. This clearly distinguishes it from siblings like generate, wait_for_generation, and execute_action, which handle creation, waiting, and post-processing actions respectively.

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?

It states the UUID comes from generate and explicitly directs follow-up actions to execute_action with the uuid, action_type, and parent_image_index. It doesn't explicitly contrast with wait_for_generation, but the context of fetching and checking state is clear enough for an agent to select it appropriately.

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

All maginary-mcp 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