Venira

Overview Schema Source Related Servers Discussions Admin

Clear caches

project_cache_clear

DestructiveIdempotent

Clears in-process caches when reads look stale after files change outside Venira; optionally target a cache type and return cleared entry counts.

Instructions

Clear in-process caches (all, read, info, list, search, recent, negative, graph, shell). Use when: reads look stale because a tool changed files outside Venira. Avoid when: normal flow: writes already invalidate caches. Output: cleared entry counts per cache.

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

Input Schema

Name	Required	Description	Default
`type`	No	Cache to clear (default all). negative = cached not_found paths; graph = import graph.	all

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv1.21.0Nov 10, 2026

changedInput schema / properties / type / description

Previous value: -"Which cache to clear."New value: +"Cache to clear (default all). negative = cached not_found paths; graph = import graph."

Addedv1.14.0Nov 5, 2026

TDQS

A4.1/5.0

Behavior3/5

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

Annotations already declare destructiveHint=true, idempotentHint=true and openWorldHint=false; the description adds that the target is in-process (not persisted) caches and that normal writes already invalidate them, which usefully tempers the destructive flag. It also discloses the return shape ('cleared entry counts per cache'), but does not say whether a clear is disruptive mid-session or how the sweeps interact.

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?

Front-loaded purpose followed by compact 'Use when / Avoid when / Output' lines; every clause carries decision-relevant information and nothing is padded.

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 single optional enum parameter with full schema coverage, the definition supplies purpose, trigger, exclusion, and the shape of the result. There is no output schema, but the description's 'Output:' line covers what would be returned.

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% and the enum already documents 'negative = cached not_found paths' and 'graph = import graph'. The description repeats the same value list without adding syntax, interactions, or consequences per type, so the schema carries the weight.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Clear in-process caches') and enumerates the cache families covered. The phrase 'in-process' usefully scopes it away from disk/OS caches, though it does not explicitly contrast with any sibling tool.

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?

Gives an explicit trigger ('reads look stale because a tool changed files outside Venira') and an explicit exclusion ('normal flow: writes already invalidate caches'), which is exactly the when/when-not split an agent needs. No alternative tool is named, but the avoid condition makes the default path obvious.

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