ansible-know-mcp

Overview Schema Source Related Servers Discussions Admin

Clear Cache

clear_cache

Idempotent

Clear Galaxy, docs, and standalone-role caches when cached data becomes stale during long-running sessions; target a specific scope or clear all caches.

Instructions

Clear server caches.

Clears Galaxy version/docs-blob caches, standalone-role v1 caches, doc manifest/page caches, or both. Useful when cached data becomes stale during long-running sessions.

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_cache"
  }
}

Input Schema

Name	Required	Description	Default
`scope`	No	Cache scope to clear: 'galaxy' (version + docs-blob + standalone-role v1), 'docs' (doc manifests), or omit to clear all caches.

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv0.9.0Aug 19, 2026

changedInput schema / properties / scope / description

Previous value: -"Cache scope to clear: 'galaxy' (version + docs-blob), 'docs' (doc manifests), or omit to clear all caches."New value: +"Cache scope to clear: 'galaxy' (version + docs-blob + standalone-role v1), 'docs' (doc manifests), or omit to clear all caches."

First observedv0.7.0Jul 7, 2026

TDQS

A3.9/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=false, idempotentHint=true and destructiveHint=false, so the safety profile is covered structurally. The description adds the useful context that what is being discarded is regenerable cache state, but it does not say whether the clear affects other concurrent sessions, whether it costs time to rebuild, or what permissions are needed.

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?

Very short and front-loaded: the one-line summary lands first, then the scope enumeration, then the motivation. The middle sentence partly duplicates the 'scope' parameter documentation, which is the only wasted motion.

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?

An output schema exists, so return values need no explanation, and with one optional parameter the definition covers what an agent needs to invoke it correctly. The remaining gap is operational side effects on concurrent work or rebuild cost, which matters for a cache-invalidation tool.

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 description coverage is 100% and the single 'scope' parameter is already documented with its three accepted values and the omit-means-all default. The description's enumeration of cache families loosely mirrors that, but adds no new syntax or default-behavior detail beyond the schema.

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 and resource ('Clear server caches') and then names the concrete cache families affected: Galaxy version/docs-blob, standalone-role v1, and doc manifest/page caches. No sibling tool performs anything resembling this, so the operation is unambiguously distinguishable from the surrounding search/get/package tools.

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?

Gives an explicit trigger condition: 'Useful when cached data becomes stale during long-running sessions.' That tells the agent when to reach for it, but there are no exclusions (e.g., don't clear mid-collection-build) and no mention of alternatives such as re-fetching a doc instead of clearing caches.

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