Skip to main content
Glama

Run QA on Results

queue_generation_result_qa
Destructive

Run or re-run official Uwear QA on existing generation results. Every image generate/edit result already gets a free AI check after delivery, so when the user asks to QA, quality check, validate, review or inspect results, first call read_generation_result_qa and use the existing check (ai_qa). Call this tool only when needed: the user wants approve/reject set by QA (mode gate), or the check could not run (ai_qa.can_recheck true: use mode observe). Do not substitute view_image for QA unless the user explicitly asks for a manual visual critique instead of the official Uwear QA pipeline. After queuing, call read_generation_result_qa for the same IDs. QA is free. QA is built for scale — validating large batches (hundreds or thousands of results). When the user is iterating on a handful of results one by one, do not queue QA on your own initiative; run it when the user asks for it or when operating at batch scale.

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": {
      "generation_result_ids": "<generation_result_ids>"
    },
    "name": "queue_generation_result_qa"
  }
}

Input Schema

NameRequiredDescriptionDefault
modeNogate (default): official QA that sets approve/reject and may retry. observe: only re-run the free AI check when it could not run (ai_qa.can_recheck); it never sets a decision and never retries.gate
max_qa_retriesNoMaximum QA-triggered retry generations to allow. Retry generations can cost additional generation credits.
generation_result_idsYesGeneration result IDs to QA. QA is free.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / mode
      Added value: +{
      +  "default": "gate",
      +  "description": "gate (default): official QA that sets approve/reject and may retry. observe: only re-run the free AI check when it could not run (ai_qa.can_recheck); it never sets a decision and never retries.",
      +  "enum": [
      +    "gate",
      +    "observe"
      +  ],
      +  "type": "string"
      +}
  2. Changed1 schema field changed
    • changedInput schema / properties / generation_result_ids / description
      Previous value: -"Generation result IDs to QA. Queued or requeued QA costs 1 credit per result."New value: +"Generation result IDs to QA. QA is free."
  3. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Goes well beyond the annotations (destructiveHint=true, idempotentHint=false) by disclosing that gate mode sets approve/reject and may trigger retries, that observe never sets a decision or retries, that the AI check itself is free but retry generations may cost credits, and that the caller should follow up with read_generation_result_qa on the same IDs. That is exactly the mutation/cost/sequencing context an agent needs.

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 purpose, then routing, then constraints — well ordered and readable. It is somewhat long and repeats the cost message ("QA is free" appears in both prose and schema, and the scale/iteration point spans two sentences that overlap).

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?

For a non-idempotent batch mutation with no output schema, the description covers preconditions, mode selection, cost, follow-up read, and batch-scale expectations. Nothing an agent needs to invoke it correctly is missing.

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

Parameters4/5

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

Schema coverage is 100%, so the schema already carries the baseline. The description still adds real meaning: it states when mode=observe applies (ai_qa.can_recheck true) and what gate does, though it never mentions max_qa_retries or the 50-ID cap outside 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?

Opens with a specific verb+resource: "Run or re-run official Uwear QA on existing generation results." It immediately distinguishes itself from read_generation_result_qa by framing that sibling as the first step and this tool as the re-run/gate path.

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 explicit routing: call read_generation_result_qa first and reuse the existing ai_qa check; only call this when the user wants approve/reject set (mode gate) or when ai_qa.can_recheck is true (mode observe). It also states an exclusion (do not substitute view_image) and a do-not-proactively-queue rule for small manual iterations.

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