Skip to main content
Glama

generated_pictures

Read-onlyIdempotent

Lists prior image creations by kind and newest first with IDs, prompts, and folders so you can reuse them in other tools.

Instructions

Read-only list of pictures made with Higgsfield before (kept on this computer for every project), newest first: id, kind, what was asked, when, folder. Free to reuse: pass an id to put_picture, remove_background, relight, or as from_pictures in generate_*. Pictures already in the project are in get_shot instead.

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": "generated_pictures"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindNoOnly pictures of this kind.
limitNoMost pictures to list, 1 to 100. Default 30.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.1.2
    • addedInput schema / properties / kind / description
      Added value: +"Only pictures of this kind."
    • addedInput schema / properties / limit / description
      Added value: +"Most pictures to list, 1 to 100. Default 30."
  2. First observedv0.1.0

TDQS

A4.3/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 safety is covered; the description adds real context beyond that: results are local to this computer, shared across every project, returned newest first, and reusable for free in downstream tools. It does not discuss pagination behavior or what happens when no pictures match, which keeps it short of a 5.

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?

Front-loaded with the read-only list statement, then the reuse guidance, then the sibling pointer — three compact moves with no filler. The parenthetical about local storage slightly interrupts the opening sentence, but nothing is wasted.

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?

There is no output schema, so disclosing the returned fields is the right call and it is done well, and the two parameters are fully documented in the schema. What is missing is minor: no statement of what an empty result looks like or whether results can be paged past the limit.

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%, with the kind enum and the 1-100 limit bound already documented in the schema, so the baseline is 3. The description mentions 'kind' only as a returned field, not as a filter, and says nothing about limit, so it adds no meaning beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Names a specific verb and resource (read-only list of pictures made with Higgsfield), states scope (kept locally, spanning every project), ordering (newest first), and enumerates the returned fields (id, kind, prompt, when, folder). It also explicitly separates itself from get_shot, which holds project pictures, so an agent can pick between the two without inspecting schemas.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives a concrete consumption path — pass an id to put_picture, remove_background, relight, or as from_pictures in generate_* — and names the alternative for the other case (pictures already in the project live in get_shot). That is explicit when-to-use plus when-to-look-elsewhere guidance.

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