Skip to main content
Glama
Sign In
coalesce-transform-mcp

coalesce-transform-mcp

Official
by Coalesce-Software-Inc
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Clear Data Cache

clear_data_cache
Destructive

Removes all cached artifacts from disk to free up space. Requires user confirmation before clearing.

Instructions

Clear the MCP server's local data cache. Removes all cached artifacts from disk.

Args:

  • confirmed (boolean, optional): Set to true after the user explicitly confirms cache clearing

Returns: { deleted: boolean, fileCount: number, totalBytes: number, message: string }

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

Input Schema

NameRequiredDescriptionDefault
confirmedNoSet to true after the user explicitly confirms the cache clearing.

Output Schema

NameRequiredDescriptionDefault
sizeMBNo
deletedNo
messageNo
fileCountNo
totalBytesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.10.1

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already indicate destructiveHint=true. The description adds that it removes all cached artifacts from disk, confirming the scope. It does not contradict annotations and provides additional context about the action's permanence, though it could mention impact on ongoing operations.

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?

Description is extremely concise: one sentence for purpose, then a clear Args and Returns section. Every sentence adds value. No unnecessary words.

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 simple cache-clearing tool with one optional parameter and an output schema, the description provides all necessary context: what it does, the safety confirmation step, and the return structure. No gaps.

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

Parameters3/5

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

Schema coverage is 100% with a description for the confirmed parameter. The tool description repeats this information without adding new semantics. Baseline score of 3 is appropriate.

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?

Description clearly states the verb 'clear' and resource 'data cache', specifying it removes all cached artifacts. No sibling tools perform cache clearing, so no differentiation needed.

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

Usage Guidelines4/5

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

Description explains when to use (to clear cache) and provides a guideline that the confirmed parameter should be set after user explicit confirmation. However, it does not explicitly discuss when not to use or alternatives, but for a simple maintenance tool, this is acceptable.

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