Skip to main content
Glama

check_pacing

Analyzes novel chapters for pacing by measuring payoff, conflict, and hook density, then flags desert stretches where reader interest may drop.

Instructions

【机器层】节奏检查:爽点/冲突/钩子密度 + 荒漠预警(去 LLM 桩)。

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_pacing"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

C2.4/5.0
Behavior2/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 hints at determinism via '机器层' (machine layer, non-LLM), which is mildly useful, but never states whether the call is read-only, what it returns (numeric densities? a warning list? thresholds?), or what 'desert warning' triggers on. The '(去 LLM 桩)' note is an internal changelog artifact rather than behavior an agent can act on.

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 short line with no filler sentences, so length is appropriate. But the structure leads with an opaque bracketed tag and ends with an implementation note, pushing the actually informative metric list into the middle and wasting the front-loaded position.

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?

For a simple one-parameter check with no output schema and no annotations, the description should at minimum convey what the response looks like (scores, thresholds, warnings) and what unit of text it expects. Neither is covered, and the jargon terms are left undefined, so an agent cannot confidently interpret results.

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?

The single required parameter 'text' has 0% schema description coverage, and the description does not compensate. It never clarifies whether 'text' means one chapter, a full outline, or a scene, nor whether any length or format constraints apply. The description only implies that pacing is evaluated over the supplied text.

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

Purpose3/5

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

The description names a concrete operation ('节奏检查') and enumerates what it measures: 爽点/冲突/钩子 density plus a 'desert' (no-payoff stretch) warning. That is more specific than a bare restatement of the name. However, the bracketed prefix '【机器层】' and the trailing '(去 LLM 桩)' are internal engineering jargon that do not help an agent distinguish this from siblings like check_ai_flavor or check_format.

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, on what stage of a manuscript, or how it relates to the many other check_* siblings. The agent must infer usage entirely from the tool name and the metric list. No exclusions or prerequisites are given.

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