Skip to main content
Glama

Kubeez

get_generation

Read-onlyIdempotent

Scope: read:generations. Fetch a SINGLE past generation by id — full detail (prompt, model, params, status, outputs, credits_deducted, error_message). Use when you have a specific id and want one row; vs get_generations which returns a paginated history. Pairs with regenerate(id, ...) for iteration: get_generation(id) → inspect params → regenerate(id, prompt='tweaked'). Returns the same row shape as one entry of get_generations.generations[].

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

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

Input Schema

NameRequiredDescriptionDefault
idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint/idempotentHint true, destructiveHint false, and closed-world, so the safety profile is covered. The description adds real value beyond that: the required scope (`read:generations`) and the shape guarantee that the row matches an entry of `get_generations.generations[]`. It stops short of describing behavior on an unknown/expired id, which keeps it from 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 scope and the core action, then the disambiguation, then the workflow — a sensible priority order with no filler sentences. The arrow-and-backtick notation (`get_generation(id) → inspect params → regenerate(id, prompt='tweaked')`) is dense and slightly code-like, but it earns its space by making the loop unambiguous.

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?

An output schema exists, so return values need not be spelled out, yet the description still lists the notable fields for quick scanning. For a one-parameter read tool, everything an agent needs to select and call it correctly — scope, disambiguation, workflow, row shape — is present.

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?

The single `id` parameter has 0% schema description coverage, so the description must carry the meaning — and it does partially, establishing that the id identifies a past generation and implying (via the `get_generations.generations[]` row-shape note) where such ids come from. It never states the id's format or what happens if the id is stale, so the coverage gap is only partly compensated.

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?

Opens with a specific verb and resource ("Fetch a SINGLE past generation by id") and immediately enumerates what detail is returned (prompt, model, params, status, outputs, credits_deducted, error_message). It explicitly distinguishes itself from `get_generations`, so an agent can pick between the single-row and history tools without opening either schema.

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?

Gives an explicit when-to-use condition ("when you have a specific id and want one row") and names the alternative with the condition that selects it (`get_generations` for paginated history). It also supplies a concrete workflow (get_generation → inspect params → regenerate with a tweaked prompt), which is exactly the guidance an agent needs for iteration.

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