Skip to main content
Glama

pending_corrections

Lists transcribed segments that still need correction and returns their original text for review; check the correction guide and glossary before editing.

Instructions

列出已转写、还没纠错的段,给出原始文字供你纠正。纠正前先看 correction_guide 和 glossary。

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

Input Schema

NameRequiredDescriptionDefault
limitNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It does disclose the read-only nature of the call implicitly ('列出') and that the payload is original text awaiting correction, but says nothing about pagination, ordering, or what happens when no pending segments exist. Adequate for a simple listing tool, but short of rich behavioral context.

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?

Two short sentences, zero filler, with the core listing behavior front-loaded and the prerequisite workflow following. Every clause carries information the agent needs.

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

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a one-parameter listing tool with no output schema and no annotations, the definition covers what it returns, what state the segments are in, and what to do before correcting. The only real hole is how the limit/pagination behaves and whether results are ordered, which is minor at this complexity level.

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 coverage is 0% and the description never mentions the single limit parameter, its default of 20, or any cap. The parameter is nonetheless a self-explanatory integer with a schema-supplied default, so the practical ambiguity is small, but the description adds no meaning beyond 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?

The description names a specific verb and resource plus a precise state filter: segments that have been transcribed but not yet corrected. That state qualifier ('还没纠错') implicitly separates it from the general list_segments sibling, and it states what the returned content is (原始文字 for correction), so an agent can identify the tool's job without opening the schema.

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?

It gives an explicit prerequisite workflow: consult correction_guide and glossary before correcting, which tells the agent the right call order. It stops short of explicit when-not-to-use guidance or naming an alternative for already-corrected segments, so it is clear context rather than a full decision rule.

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