Skip to main content
Glama

check_format

Validates TTS script formatting: checks number readability, quote closure, dash limits, one person per paragraph, long parentheses, emoticons, punctuationless runs, and exclamation marks.

Instructions

【执行层】听书(TTS)格式检查:数字可读化、引号闭合、破折号 ≤3、一人一段、括号大段、颜文字、无标点长段、感叹号(冷感调性禁用)。

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": {
      "text": "<text>"
    },
    "name": "check_format"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYes
project_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

C2.7/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden of describing behavior. It describes the ruleset that is checked, which is useful, but it does not say whether the tool only reports findings or also modifies text, whether the findings block progress, or what the results contain. For an unannotated check tool, that leaves the agent supplementing a lot from the name.

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

Conciseness3/5

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

It is a single front-loaded sentence with no filler, but the abbreviated rule names (括号大段, 颜文字) and the 【执行层】 prefix take compactness to the point where they are ambiguous. The density costs some clarity for the space it saves.

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?

For a two-parameter, unannotated check tool with no output schema, the guidelines give a solid picture of the checks performed but not of the results, severity, or workflow use. The definition is adequate for recognizing the tool's job but insufficient for invoking it confidently.

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

Parameters2/5

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

Schema description coverage is 0% for two parameters, so the description would need to compensate, yet it says nothing about what `text` covers or why `project_id` is optional. The only clue is that the rules concern prose, so the agent must guess how the project-scoped context changes the checks.

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?

The description gives a specific verb and resource ('听书(TTS)格式检查') and enumerates the exact rules being validated, so an agent can tell it apart from siblings like check_pacing or check_ai_flavor. The scope is concrete, though the compressed rule list and the 【执行层】 layer tag add some noise.

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?

There is no statement of when to run this check (for example before or after drafting, or at the release gate) and no condition that tells an agent how to choose between this check and the sibling checks. The agent must infer the timing and the workflow position from the sibling names alone.

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