Skip to main content
Glama

Uwear

by ai.uwear
OverviewDiscussionsAdmin

Generation Status

get_generation_status
Read-onlyIdempotent

Use this to check one generation job by generation_id: its status, credits and, when it failed, a safe error_message. A brief's runs are read with mcp_brief_runs. Changes nothing.

Input Schema

NameRequiredDescriptionDefault
generation_idYesThe generation ID to check. Returns compact status, avatar_id, model_id, model_slug, and use_case. UI 'Gemini Pro' maps to model_slug nano-banana-pro or nano_banana_pro_clothing.
include_snapshotNoInclude full generation settings, resource snapshots and raw prompt payloads. Large; use only for prompt recovery.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / additionalProperties
      Added value: +false
  2. Changed2 schema fields changed
    • changedInput schema / properties / generation_id / description
      Previous value: -"The generation ID to check. Returns raw payload, generation_setting, avatar_id, model_id, model_slug, and use_case. UI 'Gemini Pro' maps to model_slug nano-banana-pro or nano_banana_pro_clothing."New value: +"The generation ID to check. Returns compact status, avatar_id, model_id, model_slug, and use_case. UI 'Gemini Pro' maps to model_slug nano-banana-pro or nano_banana_pro_clothing."
    • addedInput schema / properties / include_snapshot
      Added value: +{
+  "default": false,
+  "description": "Include full generation settings, resource snapshots and raw prompt payloads. Large; use only for prompt recovery.",
+  "type": "boolean"
+}
  3. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint/idempotent/non-destructive, so 'Changes nothing' is mostly a restatement; however, the description adds genuinely new behavioral facts the annotations cannot carry — that a failed job yields a sanitized 'safe error_message' and that credits are reported per job. That is useful context for interpreting the response.

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?

Two sentences, zero filler: the identity/purpose leads, the sibling routing follows, and the safety note closes. Every clause carries information an agent would otherwise have to infer.

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?

With no output schema, the description takes on responsibility for signaling what comes back and does so at a high level (status, credits, error_message), while the schema fills in the rest. Minor gap: it says nothing about failure/pending states or how long a job may take, which matters for a polling-style status check.

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 coverage is 100% and the generation_id property description is unusually rich (returned fields, model_slug mapping, include_snapshot cost warning). The description only echoes 'by generation_id', adding no semantics beyond the schema, which is the correct baseline-3 outcome when the schema does the heavy lifting.

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 ('check one generation job by generation_id') and enumerates what is returned: status, credits, and a safe error_message on failure. It also names the sibling it is not (mcp_brief_runs), so the agent can separate it from the brief-level run listing without opening a 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?

Clearly frames the use case as a single job by ID and routes the agent to mcp_brief_runs when it actually wants a brief's runs. It does not address the other plausibly overlapping siblings (get_generation_results, mcp_read_generation, mcp_read_generation_result), so the disambiguation is helpful but incomplete.

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

All Uwear toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources