Cloudera Data Visualization MCP Server

reset_dataconnection_cache

Reset the query result cache for a data connection to clear stale or cached results and force fresh queries.

Instructions

Reset the query result cache for a specific CDV data connection. Requires ds_manage permission.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "connection_id": "<connection_id>"
    },
    "name": "reset_dataconnection_cache"
  }
}

Input Schema

Name	Required	Description	Default
`connection_id`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0May 26, 2026

TDQS

A4/5.0

Behavior3/5

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

With no annotations, the description carries the full burden. It states the action and permission but does not disclose what 'reset' entails (e.g., whether it clears all cached results, impacts performance, or has side effects). Additional detail about the operation's effect would improve transparency.

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 very concise at two sentences, front-loads the core action, and contains no unnecessary words. Every sentence adds value.

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?

Given the simple tool (one parameter, output schema exists), the description covers the essential purpose and permission. However, it omits behavioral details like cache invalidation scope. Still, it is reasonably complete for its complexity.

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?

The schema has 0% description coverage, so the description must compensate. It partially explains the parameter by linking it to 'a specific CDV data connection', but does not specify the format or how to obtain the connection_id. For a single required parameter, more explicit guidance is expected.

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 clearly states the action ('Reset'), the resource ('query result cache for a specific CDV data connection'), and the permission required. It effectively distinguishes from siblings like reset_dataset_cache by specifying 'CDV data connection'.

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?

The description implies when to use the tool (to reset cache for a CDV connection) and states a prerequisite (ds_manage permission). However, it lacks explicit guidance on when not to use it or how it compares to reset_dataset_cache, leaving some ambiguity.

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

Deploy Server