Skip to main content
Glama

List the generations made on this key's organization

generations
Read-onlyIdempotent

The organization's generations, newest first, each with its status, model, files and charge: the asset library behind generate. Filter by kind, model or status; page with before. Files are kept 30 days. Needs the key. Live from GET /v1/generations.

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

Input Schema

NameRequiredDescriptionDefault
kindNo
limitNoHow many, newest first. Default 20.
modelNoOnly this media model id.
beforeNoOnly generations created before this Unix time (seconds, or the ms next_before of the last page).
statusNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), and the description adds facts those cannot convey: newest-first ordering, a 30-day file retention window, a required key, and the upstream endpoint GET /v1/generations. That is real behavioral value beyond structured fields, though pagination limits and rate behavior are left implicit.

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?

Dense but front-loaded: the resource and return shape come first, then filtering, paging, retention, auth and source. The telegraphic fragments ('Needs the key', 'Live from GET /v1/generations') are efficient, though the run-on colon clause takes a second read.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description enumerates the returned fields (status, model, files, charge), plus ordering, filtering, pagination, retention and auth. An agent has everything needed to call it correctly and interpret the response.

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?

Schema coverage is 60%, and the description compensates by assigning purpose to each parameter group: kind/model/status are filters and before is the paging cursor. It also ties 'newest first' to limit and before semantics, which the bare integer schema for before only partially conveys.

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?

Describes the resource concretely: the organization's generations, newest first, each with status, model, files and charge, and explicitly frames it as 'the asset library behind generate', which separates it from the creation tool. It never contrasts with the singular sibling 'generation', so an agent still has a small ambiguity about which read tool to pick.

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?

Gives clear operating context: filter by kind, model or status, page with before, and it sits downstream of generate. No explicit 'when not to use' or routing to an alternative for single-record lookups, which keeps it short of a 5.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.