Skip to main content
Glama
eMCP for Evolution CMS

eMCP for Evolution CMS

Official

Job Show Tool

aimage.job.show

Retrieve an image-generation job's full state by UUID, including status, planner questions, planned steps, estimate, and result paths or URLs to track progress and answer follow-ups.

Instructions

Full state of one job: status, planner conversation (questions to answer), planned steps, estimate, results with paths and URLs.

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": {
      "uuid": "<uuid>"
    },
    "name": "aimage.job.show"
  }
}

Input Schema

NameRequiredDescriptionDefault
uuidYesJob uuid from aimage.job.create / aimage.jobs

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.2.2

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations at all, the description carries the full disclosure burden, and it does usefully enumerate the returned payload even though no output schema exists. It does not state that the call is read-only/side-effect free, nor what happens for an unknown or expired uuid, which leaves real behavioral gaps for an annotation-free tool.

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?

One compact sentence that leads with the core purpose and then lists the payload contents in a scannable order. No filler, no repetition of the title or schema.

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?

For a single-parameter read tool with no annotations or output schema, the description covers what an agent most needs to know: what comes back. Only minor gaps remain around error behavior and whether the state is a snapshot requiring re-polling.

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?

The single uuid parameter is fully documented in the schema, including its provenance (aimage.job.create / aimage.jobs), so the description adds nothing beyond it. With 100% schema coverage and one parameter, the baseline of 3 is the correct ceiling.

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?

"Full state of one job" gives a specific verb and resource, and the enumerated contents (status, planner conversation, planned steps, estimate, results with paths and URLs) make the retrieval scope concrete. It implicitly separates itself from the list-style sibling aimage.jobs by saying "one job," but never names or contrasts an alternative explicitly.

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?

The parenthetical "(questions to answer)" hints that this is where an agent goes to find pending planner prompts, which implicitly points toward aimage.job.reply. However, there is no explicit statement of when to call this versus aimage.jobs or aimage.estimate, and no guidance on polling or after-action use.

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