Skip to main content
Glama

check_title

Validate chapter titles against platform constraints, ensuring visible character minimum, length limits, and hook compliance to prevent publishing errors.

Instructions

章名合规检查:可见字数 ≥5(平台硬约束)、总长 ≤15、感叹号规则、钩子分层提醒。

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": {
      "title": "<title>"
    },
    "name": "check_title"
  }
}

Input Schema

NameRequiredDescriptionDefault
titleYes
chapter_noNo
project_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

C2.9/5.0
Behavior3/5

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

With no annotations, the description does carry real behavioral weight by disclosing the actual rule set, including that the ≥5 visible-character limit is a platform hard constraint (i.e. a blocking check) while the hook item is a tiered reminder — a meaningful distinction in severity. It does not say what the tool returns (pass/fail vs. list of violations) or confirm it is side-effect free, which is a notable gap for a validator.

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?

A single front-loaded sentence that names the purpose first and then the rule set, with no filler. It is dense but every clause carries rule information; only the terse parenthetical notation costs a little readability.

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 validator with no annotations, no output schema, and zero parameter documentation, the description should at minimum indicate the shape of the result (violations list, boolean, messages) and the role of the two optional scoping parameters. It covers the rules but not the contract, leaving an agent unable to predict the response.

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% across 3 parameters, so the description must compensate and largely fails: it never mentions `title`, `chapter_no`, or `project_id`, nor explains what the optional project/chapter context changes. Only the implicit subject matter (章名) hints at the `title` argument.

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+resource (章名合规检查) and enumerates the concrete rules enforced: visible character count ≥5, total length ≤15, exclamation-mark rules, and a hook-tiered reminder. This clearly separates it from siblings like check_format or check_pacing, which operate on different content dimensions, though it never names an alternative explicitly.

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 call this versus the other check_* tools, nor any prerequisite (e.g. run before publishing, after drafting a title). Usage is only inferable from the word 检查 in the name. No exclusions or when-not guidance is present.

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