Skip to main content
Glama

Generate

generate

Start a generation (charges credits up front; refunded if it fails or is cancelled). Returns the job; poll with wait_for_generation. Above the workspace's confirm threshold the call returns status: confirmation_required with the quoted credits — ask the user, then call again with confirm_credits equal to that quote. wait_seconds (≤ 25) blocks for quick 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": {
      "model_id": "<model_id>",
      "input": "<input>"
    },
    "name": "generate"
  }
}

Input Schema

NameRequiredDescriptionDefault
inputYes
model_idYes
wait_secondsNo
confirm_creditsNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.4/5.0
Behavior5/5

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

Goes well beyond the annotations: it discloses the financial side effect (credits charged up front, refunded on failure or cancellation), the confirmation gate keyed to a workspace threshold, and the exact sentinel state (`status: confirmation_required`) that changes the required follow-up action. These are consequences an agent could not derive from readOnlyHint/destructiveHint.

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?

Three sentences, each load-bearing: cost/return, confirmation flow, blocking wait. Information is front-loaded with the credit charge and confirmation branch stated before the optional tuning param, and the parentheticals are compact rather than padded.

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?

An output schema exists, so return-value shape needn't be described, and the description still flags the one status value that changes agent behavior. The remaining gap is the untyped `input` payload — for a generative tool, no hint about what that object should contain is a real omission, though the mutation, cost, and follow-up semantics are otherwise fully covered.

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?

Schema description coverage is 0%, so the description must carry the parameter burden. It does well on the two non-obvious params — `wait_seconds` (≤ 25, blocking behavior, intended for quick models) and `confirm_credits` (must equal the quoted credits) — but says nothing about `model_id` or the free-form `input` object, which is an open `additionalProperties: true` bag and the largest source of invocation risk.

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+resource ('Start a generation') and immediately clarifies that it returns a job rather than the finished asset, routing to `wait_for_generation` for polling. It is clearly distinguishable from siblings like cancel_generation or get_generation. It stops short of saying what kind of generation (image/video/etc.) the model_id drives, which keeps it 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 Guidelines5/5

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

It gives explicit routing ('poll with `wait_for_generation`'), an explicit conditional flow for the confirm-threshold case (ask the user, then re-call with `confirm_credits` equal to the quoted amount), and guidance on when `wait_seconds` is worth using ('blocks for quick models'). An agent knows both the happy path and the escalation path without inference.

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