Skip to main content
Glama

Read QA Results

read_generation_result_qa
Read-onlyIdempotent

Read the official Uwear QA check of existing generation results. Call this first when the user asks to QA/check/validate/review generated outputs: most image results already have a free AI check. ai_qa gives the state (checking, passed, issues, unavailable, not_checked, not_supported) and ai_qa_json its structured details; qa_status/qa_decision are the approve/reject QA only. The AI check is an opinion, separate from the result's review decision. Summarize the structured check and issues, not a manual view_image opinion. Queue QA only when needed.

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

Input Schema

NameRequiredDescriptionDefault
generation_result_idsYesGeneration result IDs to read QA for

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already cover safety (readOnly, idempotent, non-destructive, closed-world), and the description adds real context beyond them: the 'most image results already have a free AI check' availability note, the enumeration of possible ai_qa states, and the semantic distinction between the AI opinion and the human review decision. It stops short of stating batching limits or latency, but it goes well past what the annotations provide.

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?

Purpose is front-loaded in the first clause, followed by trigger, field mapping, and the anti-pattern warning in descending priority. Every sentence carries distinct information, including the output-field disambiguation that the missing output schema makes necessary.

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?

With no output schema, the description compensates by naming the return fields (ai_qa, ai_qa_json, qa_status, qa_decision) and enumerating the state values, and it tells the agent how to report results ('summarize the structured check and issues'). Nothing needed to call or interpret this tool correctly is missing.

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% for the single parameter, so the schema already documents generation_result_ids. The description adds no format, ordering, or partial-failure semantics for the ID list, so the baseline of 3 applies.

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 ('Read the official Uwear QA check of existing generation results') and immediately disambiguates the returned fields: ai_qa holds the state, ai_qa_json the structured details, while qa_status/qa_decision are the separate approve/reject QA. An agent can tell this apart from related read tools without opening any 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?

'Call this first when the user asks to QA/check/validate/review generated outputs' gives an explicit trigger, and 'Queue QA only when needed' supplies the exclusion that routes to the queue sibling. It also warns against substituting a manual view_image opinion, closing the most likely misuse path.

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