Skip to main content
Glama

My generations

list_generations
Read-only

The latest pictures and videos of this account (newest first) with job ids and download links. Free.

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

Input Schema

NameRequiredDescriptionDefault
kindNo
limitNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the description is not carrying the safety burden. It still adds real behavioral content beyond the annotations: the ordering (newest first), the returned fields (job ids plus download links), and the cost trait ("Free"), which meaningfully separates it from the credit-consuming generate_* siblings. Pagination and default page size remain undisclosed.

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?

Two short sentences, front-loaded with the resource and its contents; the one-word "Free." fragment is terse but earns its place as the cost disclosure. No filler, though the abrupt fragment slightly weakens polish.

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

Completeness3/5

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

For a no-required-param, two-parameter listing tool with no output schema, the purpose and return content are adequately covered. The gaps are the undocumented parameters and the absent paging behavior, which matter because a caller cannot tell how to retrieve more than one page.

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

Parameters2/5

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

Schema description coverage is 0%, so the description is the only place parameter meaning could live, yet neither `kind` nor `limit` is mentioned. "Pictures and videos" loosely hints at the kind enum, but nothing explains the 40-item cap, the default limit, or whether omitted kind means all.

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 concrete resource and scope: the latest pictures and videos of this account, newest first, with job ids and download links. That is clearly distinguishable from generate_* and get_job siblings, though it never names a sibling or explicitly contrasts itself with them.

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

Usage Guidelines2/5

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

No guidance on when to use this versus get_job or the generate_* tools, and no mention of prerequisites such as authentication or account context. The agent must infer that this is the account-wide history listing.

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.

Resources