cdisc-library-mcp-server

cache.invalidate

Invalidate cached entries by matching their keys against a substring or regular expression pattern.

Instructions

Invalidate cache entries whose URL matches a substring or regex.

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": "cache.invalidate"
  }
}

Input Schema

Name	Required	Description	Default
`contains`	No	Substring to match against cached keys
`regex`	No	JavaScript regex string to match against cached keys

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jun 12, 2026

TDQS

A3.5/5.0

Behavior2/5

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

No annotations provided, so description carries full burden. It only says 'Invalidate' (mutating) but gives no detail on side effects, safety, or scope (e.g., whether multiple entries can be invalidated). Minimal disclosure.

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?

Single sentence, no redundancy. Front-loads the core purpose efficiently.

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

Completeness3/5

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

For a simple tool with 2 optional params and no output schema, description covers key usage but lacks details like behavior when no match or multiple matches. Adequate but not fully complete.

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%, so baseline is 3. Description adds context about matching URLs, but parameters are already described in schema. Minimal added value.

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 tool invalidates cache entries, specifying matching by URL substring or regex. This is a specific verb+resource, distinguishing it from siblings like cache.clear.

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?

Description implies usage for targeted invalidation but does not explicitly state when to use vs alternatives (e.g., cache.clear) or provide any exclusions. Usage context is weak.

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