Skip to main content
Glama

Kubeez

regenerate

Scope: generate:media. Re-run a past media generation with optional overrides. Use after critique flags an issue: regenerate(id, prompt='same concept but fix the warped hand'). Original row's prompt / model / aspect_ratio / source_media_urls / duration are reused unless you override them. Overrides: prompt (replaces original), seed (force a new seed; 0 = let provider pick), aspect_ratio, negative_prompt, variant_count (1-4 — fans out N parallel calls and returns N generation_ids). Only works on media_generations rows owned by the caller. Music / separation / dialogue regeneration is not supported via this tool — call the original tool again. Cost is identical to a fresh generate_media — confirm with the user before calling, especially for per-duration video models.

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

Input Schema

NameRequiredDescriptionDefault
idYes
seedNo
promptNo
aspect_ratioNo
variant_countNo
negative_promptNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.9/5.0
Behavior5/5

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

Annotations only say readOnlyHint=false, idempotentHint=false, openWorldHint=true, destructiveHint=false. The description adds non-obvious behavior well beyond that: reuse of the original prompt/model/aspect_ratio/source_media_urls/duration, caller-ownership restriction, seed=0 meaning provider-chosen, and that variant_count fans out N parallel calls returning N generation_ids. The cost warning is real operational context the annotations cannot convey.

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 scope and action, and every sentence carries information — nothing is filler. It is dense and slash-heavy though, packing reuse rules, override list, ownership, exclusions, and cost into one block, which slightly taxes scanning even if nothing is wasted.

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?

Output schema exists, so return values need not be explained, yet the description still notes N generation_ids for fan-out. For a cost-bearing, ownership-scoped mutation with 6 parameters at 0% schema coverage, the definition covers inheritance rules, override behavior, preconditions, and exclusions — nothing needed to call it correctly is missing.

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

Parameters5/5

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

Schema coverage is 0%, so the description carries the full burden and does: it explains prompt replaces the original, seed forces a new seed with 0 as provider-pick sentinel, variant_count is bounded 1-4 with parallel fan-out semantics, and that unspecified fields inherit the original row. This is meaningfully more than the bare property names and integer defaults in 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?

Specific verb+resource with scope declared up front ("Scope: generate:media"), then "Re-run a past media generation with optional overrides." It draws a hard boundary against generate_media-style siblings by stating that music/separation/dialogue regeneration is not supported here. An agent can distinguish this from generate_media 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?

Explicit trigger ("Use after `critique` flags an issue"), explicit exclusion (music/separation/dialogue must go back to the original tool), and an explicit precondition requiring user confirmation because cost equals a fresh generate_media. When-to-use, when-not-to-use, and the alternative are all named.

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