Skip to main content
Glama

generate_quality_report

Persist measured decode, stream, and audio checks plus explicit manual review requirements to document quality evidence and flag review needs.

Instructions

Persist measured decode/stream/audio checks and explicit manual review requirements.

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": {
      "input": "<input>",
      "output": "<output>"
    },
    "name": "generate_quality_report"
  }
}

Input Schema

NameRequiredDescriptionDefault
inputYes
outputYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

D1.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=false, and openWorldHint=false, so the safety profile is covered. The description adds only that results are persisted, without saying where they are written, whether an existing report is overwritten (relevant given idempotentHint=false), or whether it requires prior measurement steps.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is short, but the brevity comes from compressing three unrelated concepts into one slash-delimited phrase rather than from front-loading the essential information. There is no lead sentence stating plainly what the tool produces or where.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/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 values need not be explained, but two mandatory string parameters with 0% schema coverage are left uninterpreted. For a mutating persistence tool whose annotation set explicitly denies idempotency, the absence of any statement about write target or overwrite behavior is a real gap.

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

Parameters1/5

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

Schema description coverage is 0% and the two required parameters are literally named 'input' and 'output' with no type detail beyond string. The description gives no indication of what belongs in 'input' (a path? a checks payload?) or 'output' (a destination path?), leaving both parameters entirely opaque.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The verb 'persist' suggests a write operation, but the object is a dense noun pile ('measured decode/stream/audio checks and explicit manual review requirements') rather than a named artifact. It never says it writes a quality report file, and nothing distinguishes it from diagnostic siblings like inspect_audio_levels, detect_clipping, or inspect_render.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

No when-to-use guidance, no prerequisites, and no mention of alternatives. An agent cannot tell whether this should be called after the inspect/analyze tools, before export, or independently, nor what conditions make a 'manual review requirement' applicable.

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