Skip to main content
Glama

Get a dub's quality report

get_quality
Read-only

Reedapt's check of a finished dub: how many lines it checked, which it flagged, which it fixed itself (shortened or voiced again) and how many are left for a person to review.

Instructions

Reedapt's check of a finished dub: how many lines it checked, which it flagged, which it fixed itself (shortened or voiced again) and how many are left for a person to review. checked is false until the check has run, a few minutes after the dub completes. Read this before handing a dub over, and tell the person which lines to review.

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": {
      "dub_id": "<dub_id>"
    },
    "name": "get_quality"
  }
}

Input Schema

NameRequiredDescriptionDefault
dub_idYesThe dub's id, such as dub_…

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.2.0

TDQS

A4.3/5.0
Behavior4/5

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

With readOnlyHint and openWorldHint already declared, the description still adds real value: it discloses that `checked` is false until the check has run, roughly a few minutes after the dub completes, which affects call timing. It also explains what the report distinguishes (flagged vs. auto-fixed vs. awaiting human review). It does not describe failure modes for an incomplete or nonexistent dub.

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?

Front-loads what the report is, then the timing caveat, then the action. Three sentences, no filler, and the parenthetical '(shortened or voiced again)' earns its place by clarifying what an auto-fix means.

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?

There is no output schema, so the description carries the burden of explaining return values, and it does so by listing the categories of information returned plus the `checked` sentinel. For a single-parameter read tool this is complete enough for an agent to call it and interpret the result correctly.

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?

The single `dub_id` parameter is fully documented in the schema ('The dub's id, such as dub_…'), and the description adds nothing further about its format or sourcing. With 100% schema coverage the baseline of 3 applies; the description neither helps nor hurts parameter interpretation.

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?

Names a specific verb and resource ('Reedapt's check of a finished dub') and enumerates exactly what the report contains: lines checked, flagged, self-fixed (shortened or voiced again), and remaining for human review. This clearly separates it from siblings like get_dub or get_transcript, which would not describe an automated quality pass.

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 an explicit condition for use: 'Read this before handing a dub over.' It also prepares the agent for timing by noting the check runs a few minutes after the dub completes. It does not name alternatives (e.g., wait_for_dub for gating until `checked` flips), so slightly short of fully prescriptive guidance.

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