Skip to main content
Glama
Podcast MCP
by calebn

low_confidence_words_tool

Lists transcript words below a confidence threshold for human review, defaulting to the project's unsure-word line so editors can target uncertain transcription results.

Instructions

List words below a confidence threshold for human review.

threshold defaults to the project's unsure-word line, the config key analysis.unsure_word_confidence (0.7 as shipped), the same line the mapped unsure flag, the refine brief and bulk approve use. Suppressed words are not listed.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "low_confidence_words_tool"
  }
}

Input Schema

NameRequiredDescriptionDefault
thresholdNo
project_pathNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.1.4
    • addedInput schema / properties / threshold / anyOf
      Added value: +[
      +  {
      +    "type": "number"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • changedInput schema / properties / threshold / default
      Previous value: -0.7New value: +null
    • removedInput schema / properties / threshold / type
      Removed value: -"number"
  2. Changed4 schema fields changedv0.1.1
    • addedInput schema / properties / project_path / anyOf
      Added value: +[
      +  {
      +    "type": "string"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • addedInput schema / properties / project_path / default
      Added value: +null
    • removedInput schema / properties / project_path / type
      Removed value: -"string"
    • removedInput schema / required
      Removed value: -[
      -  "project_path"
      -]
  3. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries the full burden; it does disclose the default threshold source and that suppressed words are excluded from results, which is useful beyond the schema. It does not clarify that the operation is read-only, nor mention result ordering, pagination, or volume expectations for a review-oriented list.

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 the core action, then one dense clause explaining the default. The config-key sentence is slightly convoluted but every clause adds real information about the threshold semantics.

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

Completeness3/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 needn't be described, and the threshold default is well covered. The unexplained project_path and the absence of any note on read-only safety or result volume leave gaps for a multi-project tool.

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 0% for two parameters, and the description compensates well for 'threshold' by naming the config key, its shipped value (0.7), and the related unsure flag. 'project_path' receives no explanation at all, so half the parameter surface remains undocumented.

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

Purpose4/5

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

States a specific verb and resource — 'List words below a confidence threshold' — plus the purpose, 'for human review'. The confidence metric implicitly separates it from siblings like low_audibility_words_tool, though no sibling is named explicitly.

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

Usage Guidelines3/5

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

'For human review' implies the intended workflow and 'Suppressed words are not listed' clarifies a scoping behavior, but there is no explicit when-to-use versus when-not guidance and no alternative tool is referenced.

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

Deploy Server

Other Tools