Zhenzhen Image MCP

get_image_batch

Read-onlyIdempotent

Restores a session's batch task IDs, provider task IDs, and last observed statuses from a local checkpoint, without querying providers, submitting jobs, or waiting for image generation.

Instructions

免费读取本地持久化检查点，恢复该会话所有 task_id/provider_task_id/最后观察状态；不查询供应商、不提交、不等待成图。

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": {
      "checkpointer": "<checkpointer>",
      "thread_id": "<thread_id>"
    },
    "name": "get_image_batch"
  }
}

Input Schema

Name	Required	Description	Default
`thread_id`	Yes	稳定的本地检查点命名空间/会话键，1–128字符。
`checkpointer`	Yes	稳定的本地检查点命名空间/会话键，1–128字符。

Output Schema

Name	Required	Description	Default
`note`	Yes
`tasks`	Yes
`status`	Yes
`next_tool`	Yes
`thread_id`	Yes
`checkpointer`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedv0.4.0Oct 23, 2026

addedOutput schema / $defs / ImageResult / properties / auto_poll_interval

Added value: +{
+  "title": "Auto Poll Interval",
+  "type": "integer"
+}

addedOutput schema / $defs / ImageResult / properties / idempotency_key

Added value: +{
+  "title": "Idempotency Key",
+  "type": "string"
+}

addedOutput schema / $defs / ImageResult / properties / reused

Added value: +{
+  "title": "Reused",
+  "type": "boolean"
+}

changedOutput schema / properties / status / enum

Previous value: -[
-  "ACCEPTED",
-  "ATTENTION_REQUIRED",
-  "SNAPSHOT"
-]New value: +[
+  "ACCEPTED",
+  "ATTENTION_REQUIRED",
+  "SNAPSHOT",
+  "COMPLETED"
+]

First observedv0.3.0Oct 20, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive/closed-world, so the safety profile is covered. The description adds real context beyond that: the read is free, it is local-persistence only, and it performs no provider call, no submission, and no wait — which tells an agent this cannot fetch fresh upstream status.

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 compact sentence with the key property (free, local) front-loaded and the exclusions trailing. No wasted words, though the semicolon-chained run-on is slightly dense.

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 an output schema present and rich annotations, the description need not explain returns. It covers the essential operational semantics and the offline limitation; only the checkpointer-vs-thread_id distinction is left unresolved.

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 the baseline is 3. Notably, both thread_id and checkpointer carry identical schema text ('稳定的本地检查点命名空间/会话键'), and the description does nothing to disambiguate the two required keys beyond saying '该会话', leaving a real semantic gap.

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?

The description states a specific action and resource: a free read of a local persisted checkpoint that restores all task_id/provider_task_id/last-observed state for the session. The closing negative clauses (no provider query, no submit, no wait) implicitly contrast it with submit_image_batch and wait_image_task, so an agent can tell it apart even without named siblings.

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 gives a clear condition for use: cheap, offline recovery of session state that avoids contacting the vendor. It does not name an alternative tool by name or state an explicit when-not case beyond the negations, so it stops short of full routing guidance.

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

Deploy Server