Skip to main content
Glama

Recent gallery items

gallery

Lists recent generation results in reverse chronological order with IDs, workflows, status, and prompts, optionally filtered by search text. Use returned IDs to animate or edit images in generate.

Instructions

Lists recent results (newest first) with id, workflow, status and prompt, optionally filtered by a search text. Use the ids as images in generate, e.g. to animate an image or edit it further.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "gallery"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
searchNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/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 does disclose the sort order (newest first) and the shape of returned records, which is genuinely useful. It is silent on scope (workspace-wide? per user?), pagination beyond the limit parameter, and whether results are truncated, so an agent can't reason about completeness of the listing.

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?

Two tight sentences with no filler; the core behavior and the return fields are front-loaded, and the follow-on usage tip is short. Every clause earns its place.

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 two-parameter, read-only listing with no output schema and no annotations, the description covers purpose, ordering, and returned fields, which is most of what an agent needs. The remaining gaps are scope and pagination behavior, which are secondary for a simple recent-items list.

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 coverage is 0%, so the description should compensate. It explains the 'search' parameter ('optionally filtered by a search text') but says nothing about 'limit', leaving the default of 10 and the max of 50 to be discovered from the schema, with no guidance on when to raise it.

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 ('Lists recent results') plus concrete details: newest-first ordering and the returned fields id, workflow, status, prompt. It doesn't explicitly contrast with siblings like figures or inspect_image, so the agent must infer the boundary from names alone.

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 second sentence gives useful downstream guidance ('use the ids as images in generate'), which implies this is the discovery step before generation or editing. However, there is no explicit when-to-use/when-not statement and no comparison against alternatives such as figures for browsing older or different items.

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