Retrieve recent image generation history with limit and offset pagination; returns no records when history is disabled, reflecting current availability.
List recent image generations history.
Returns no records when history is disabled (disable_history config or
ZIMAGE_DISABLE_HISTORY env var), even if the database holds older entries.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | ||
| offset | No |
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description must carry the full behavioral burden. It does disclose a non-obvious trait — the tool returns zero records when history is disabled even though older rows exist in the database — but omits sort order, pagination behavior, and whether the operation is read-only (only implied by 'List').
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two short sentences, purpose front-loaded, and the disabled-history caveat earns its place because it prevents a misinterpretation of empty results. Slightly verbose parenthetical detail about config/env var but still tight.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
An output schema exists, so return shapes need not be described, and the empty-result caveat is valuable. However, for a paginated listing tool with two undocumented parameters, the description leaves the agent without guidance on page size or how to retrieve older entries.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Two parameters exist (limit, offset) with 0% schema description coverage, and the description never mentions them. The word 'recent' vaguely hints at ordering but does not explain paging, defaults (10/0), or maximum values, so it fails to compensate for the schema gap.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Specific verb ('List') plus specific resource ('recent image generations history'), which an agent can clearly distinguish from siblings 'generate' and 'list_models'. It stops short of explicitly naming those siblings as alternatives, but the resource boundary is unambiguous.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Usage is only implied ('recent generations history'), with no statement of when to prefer this over list_models or generate, and no prerequisites. The one genuine guideline given is a negative condition: results are empty if history is disabled via config or env var.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.