Skip to main content
Glama

List characters and products

figures

Lists saved recurring people and products with names, kinds, and reference-sheet gallery IDs; pass a saved name to the scene generator to place that subject into a new scene.

Instructions

Lists the saved figures (recurring people and products) with name, kind and the gallery id of their reference sheet. Pass a name in generate.figures to put the figure into a new scene.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior3/5

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

No annotations are supplied, so the description must carry the behavioral burden, and 'Lists' does imply a non-mutating read. It usefully discloses the returned fields (name, kind, gallery id of the reference sheet), but says nothing about ordering, pagination, size limits, or whether the list is complete — real gaps for a discovery tool with no annotation coverage.

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 sentences, each earning its place: the first defines the resource and its return shape, the second routes the result into generate.figures. Return fields are front-loaded before the follow-up hint, and there is no redundant restatement of the title.

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 zero-parameter read with no output schema, describing the three returned fields (name, kind, gallery id) is exactly the right compensation. The only missing pieces are ordering/pagination behavior and any hint about how large the figure set may be.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so there is no per-parameter meaning to add; baseline 4 applies. The description correctly requires no arguments and instead uses its space to explain how the outputs feed a different tool.

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 opens with a specific verb and resource ('Lists the saved figures') and even defines the domain term as 'recurring people and products', so an agent knows exactly what this returns. It stops short of naming a sibling it is distinct from (e.g. gallery or create_figure), which is what separates a 4 from a 5.

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?

The second sentence gives a concrete follow-up path: take a returned name and pass it to generate.figures to place the figure in a scene. That is real when-to-use guidance chaining this discovery call to the generation call, though there is no explicit exclusion or statement of when another listing tool would be preferred.

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