Skip to main content
Glama
Sign In
Kiln

Kiln

by codeofaxel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

await_generation

Read-only

Polls a generation job until it finishes or times out, then returns the final status so agents can wait for a 3D model to be ready.

Instructions

Wait for a generation job to complete and return the final status.

        Polls the provider until the job reaches a terminal state or the
        timeout is exceeded.  Useful for agents that want to block until
        a model is ready.

        Args:
            job_id: Job ID from ``generate_model``.
            provider: Provider that owns the job.
            timeout: Max seconds to wait for generation (default 600 = 10 min).
            poll_interval: Seconds between polls (default 10).

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": {
      "job_id": "<job_id>"
    },
    "name": "await_generation"
  }
}

Input Schema

NameRequiredDescriptionDefault
job_idYesJob ID from ``generate_model``.
timeoutNoMax seconds to wait for generation (default 600 = 10 min). Default: 600.
providerNoProvider that owns the job. Default: "meshy".
poll_intervalNoSeconds between polls (default 10). Default: 10.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv1.5.1
    • addedInput schema / properties / job_id / description
      Added value: +"Job ID from ``generate_model``."
    • changedInput schema / properties / poll_interval / description
      Previous value: -"Default: 10."New value: +"Seconds between polls (default 10). Default: 10."
    • changedInput schema / properties / provider / description
      Previous value: -"Default: \"meshy\"."New value: +"Provider that owns the job. Default: \"meshy\"."
    • changedInput schema / properties / timeout / description
      Previous value: -"Default: 600."New value: +"Max seconds to wait for generation (default 600 = 10 min). Default: 600."
  2. Changed6 schema fields changedv1.5.0
    • removedInput schema / properties / poll_interval / default
      Removed value: -10
    • addedInput schema / properties / poll_interval / description
      Added value: +"Default: 10."
    • removedInput schema / properties / provider / default
      Removed value: -"meshy"
    • addedInput schema / properties / provider / description
      Added value: +"Default: \"meshy\"."
    • removedInput schema / properties / timeout / default
      Removed value: -600
    • addedInput schema / properties / timeout / description
      Added value: +"Default: 600."
  3. First observedv0.1.0

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds real behavior: it polls the provider repeatedly until a terminal state or the timeout is exceeded. However, it never says what happens on timeout (error vs. returning a non-terminal status) or what 'final status' contains, which is the key behavioral question for a blocking call.

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 action and outcome in the first sentence, then the polling mechanism, then a usage cue. The trailing 'Args' section duplicates schema text and could be dropped, but overall the text is tight and well-ordered.

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?

There is no output schema, so the description carries the burden of explaining the return value, yet it only says 'final status' without describing its fields or terminal states. With four parameters fully documented in the schema the input side is complete, but the timeout-outcome and return-shape gaps leave an agent guessing at the result of a blocking call.

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 100% and the 'Args' block restates the same text verbatim, including defaults already in the schema. No additional semantics are conveyed, such as what a smaller poll_interval costs or how timeout interacts with provider-specific job durations, so this lands at the baseline 3.

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?

States a specific verb and resource ('Wait for a generation job to complete') plus the outcome ('return the final status'), and the phrase 'block until a model is ready' implicitly separates it from the non-blocking 'generation_status' sibling. An agent can tell what this does without opening the schema.

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 a clear selection condition: use this when the agent wants to block until the model is ready, which contrasts with polling status manually. It stops short of naming the alternative ('generation_status') or stating when not to use this (e.g., for long jobs where blocking is undesirable), so it is context-rich but not fully prescriptive.

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

Deploy Server

Other Tools