Skip to main content
Glama

Clear attachment cache

alibaba_clear_cache
DestructiveIdempotent

Clears locally cached attachment files without altering Alibaba data. Use it to free disk space or reset the private attachment cache while leaving conversations unchanged.

Instructions

Delete files in the private local attachment cache. This does not change anything on Alibaba.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.4

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare destructive, non-read-only, idempotent, and closed-world behavior. The description adds useful context by specifying what is destroyed, namely files in the private local attachment cache, and that Alibaba state is unaffected; it does not discuss recoverability or permissions, but it is consistent with the annotations.

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?

The description is two short sentences with the action and scope front-loaded. Every sentence adds useful information: the first states what is deleted and where, and the second prevents confusion about Alibaba-side effects.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a zero-parameter local mutation, the annotations carry the safety profile and the description carries the scope and side-effect context. Nothing essential for selecting and invoking this tool is missing.

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 has zero parameters, so there is no parameter meaning for the description to add beyond the schema. The baseline for a parameterless tool applies, and the description does not introduce unnecessary parameter-like details.

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?

The description uses a specific verb, "Delete files," and a precise resource, "private local attachment cache," and the second sentence clarifies that Alibaba is unaffected. This lets an agent distinguish it from sibling tools that list or download Alibaba attachments.

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

Usage Guidelines3/5

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

Use is implied by the cache-clearing purpose and the local-only scope, but the description does not explicitly state when to use it, when not to use it, or any prerequisites. No sibling clear-cache alternative is named, so the guidance remains adequate but incomplete.

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