Skip to main content
Glama

clean_cache

Destructive

Provides a compatibility placeholder for cache-cleaning requests, returning success without deleting cached data. Use clean_stream_temp_file to remove streaming temporary files.

Instructions

清理缓存 兼容占位接口,当前返回成功但不执行清理。流式临时文件清理请使用 clean_stream_temp_file。

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior1/5

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

The description says the call returns success but performs no cleaning, i.e. it is effectively a read-only stub. Annotations declare readOnlyHint=false and destructiveHint=true, so the two sources describe opposite risk profiles. The description is likely the more accurate account, but the conflict means an agent trusting annotations would badly misjudge the call.

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?

Three short clauses, front-loaded with the purpose, then the caveat, then the alternative. Every clause carries information an agent needs and none is redundant.

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 stub with no parameters and no output schema, the description covers purpose, actual behavior, return semantics, and the correct alternative. It does not address the mismatch with its own destructive annotation, which leaves an agent with an unresolved safety question.

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

Parameters4/5

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

The tool takes zero parameters, so there is no parameter semantics to explain; the schema is an empty object with additionalProperties=true. Baseline 4 applies, and the description correctly says nothing about inputs rather than inventing any.

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?

States a specific verb+resource (清理缓存) and immediately qualifies it: a compatibility placeholder that returns success without doing anything. It also names the sibling (clean_stream_temp_file) that handles the real streaming-temp-file case, so the agent can distinguish the two without opening either schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly states the call is a no-op and routes the agent to clean_stream_temp_file for actual streaming temp file cleaning. Both the when-not condition (nothing is cleaned) and the alternative are given, leaving nothing to inference.

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

Deploy Server

Other Tools