Skip to main content
Glama
Sign In
Local Image MCP

Local Image MCP

by fz-liu
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

get_result

Look up an image-generation job by prompt_id to check if it is queued, running, completed, or failed; set return_image=true to retrieve the PNG result when available.

Instructions

用 generate 返回的 prompt_id 查询任务状态：queued / running / ok / failed / unknown（历史和队列未找到）。Look up a job by prompt_id; unknown means neither history nor queue contains it. 可用 return_image=true 取回图片内容。Use return_image=true for image content.

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": {
      "prompt_id": "<prompt_id>"
    },
    "name": "get_result"
  }
}

Input Schema

NameRequiredDescriptionDefault
prompt_idYesgenerate 返回的 prompt_id。The prompt_id returned by generate.
return_imageNo为 true 且图片≤2MB 时返回 PNG 内容块。Return image content when true and file is <=2MB.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.2

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It usefully defines 'unknown' as absent from both history and queue and notes the 2MB image cap, but says nothing about whether the call is read-only, how often it should be polled, or what is returned for 'failed' (error text?). That leaves meaningful behavioral gaps for a no-annotation tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The status list and prompt_id origin are front-loaded, which is good. However, every sentence is duplicated in Chinese and English, roughly doubling length without adding information for a single reader.

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?

For a simple 2-parameter lookup with no annotations and no output schema, the description covers the state machine but not the shape of the response — what fields accompany each status, what 'failed' surfaces, or what the non-image response looks like. Adequate but leaves real gaps.

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, including that prompt_id comes from generate and that return_image returns a PNG under 2MB. The description largely echoes the schema, adding only the status vocabulary, so baseline 3 applies.

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 and resource ('look up a job by prompt_id') and enumerates the possible states (queued/running/ok/failed/unknown), which no sibling would do. It ties itself to the output of 'generate', though it never explicitly distinguishes itself from the sibling tool named 'status', leaving a small ambiguity.

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?

Gives clear context: use the prompt_id returned by generate, and set return_image=true when image content is needed. It does not give explicit when-not guidance (e.g., when to prefer 'status' over this tool, or whether polling is expected), so it stops short of the 5 mark.

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

Deploy Server

Other Tools