Skip to main content
Glama
獬豸(Xiezhi)小说投稿评审 MCP Server

獬豸(Xiezhi)小说投稿评审 MCP Server

by proteus-vue

cache_stats

Reports cache hit statistics and clears cached review data; set clear=false to view statistics only.

Instructions

缓存命中统计与清空能力(clear=false 只看)。

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

C2.4/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. It hints at a destructive clear capability without saying what gets destroyed, whether it is reversible, what permissions are required, or what the statistics response looks like; the only behavioral statement depends on a nonexistent flag.

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 padding, which is good, but the compression produces ambiguity: the parenthetical reads as a parameter reference rather than a description of behavior.

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 zero-parameter tool with no output schema, the description should say what statistics are returned and that it is read-only. Instead it introduces an unactionable clear flag and leaves the return shape and the relationship to cache_clear unexplained.

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 schema declares zero parameters, which normally gives a baseline of 4, but the description invents a 'clear=false' flag that the agent cannot supply. That is actively misleading rather than merely uninformative, so it scores below baseline.

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 phrase '缓存命中统计' states a specific resource (cache hit statistics), but the second half ('清空能力', clear capability) muddies the purpose: it implies this tool can clear the cache, which conflicts with the existence of a sibling named cache_clear. The agent can guess the main function but cannot reliably tell it apart from the sibling.

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?

'clear=false 只看' is the only usage hint, and it refers to a parameter that does not exist in the schema, so the guidance cannot be acted on. No alternative is named and no condition for choosing cache_stats over cache_clear is given.

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