Cloudera Data Visualization MCP Server

toggle_cprofile

Enable or disable cProfile profiling for a specific Cloudera Data Visualization server function, with options to strip directory names and print callees or callers.

Instructions

Toggle cProfile profiling on/off for a CDV server function. Requires sys_viewlogs permission. If profiling is already enabled, calling this disables it. strip_dirnames, print_callees, print_callers: 'yes' or 'no'.

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

Input Schema

Name	Required	Description	Default
`module`	No
`owner`	No
`func`	No
`strip_dirnames`	No
`print_callees`	No
`print_callers`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0May 26, 2026

TDQS

B3.2/5.0

Behavior2/5

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

No annotations are provided, so the description must disclose all behavioral traits. It covers permission, toggle behavior, and valid values for three parameters. However, it omits side effects, idempotency, and behavior for the 'module', 'owner', and 'func' parameters. The description is insufficiently transparent for a tool with 6 parameters and no schema documentation.

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?

The description is three sentences with no redundant information. It front-loads the core purpose and permission, then covers toggle behavior and a brief parameter hint. However, clarity could be improved by explicitly listing all parameters.

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

Completeness2/5

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

Given the tool's complexity (6 parameters, toggle behavior, permission requirement) and lack of annotations, the description is incomplete. It fails to explain three parameters, does not describe the output (despite an output schema existing, but not shown), and offers no usage context beyond the toggle action.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must fully explain parameters. It provides valid values ('yes' or 'no') for three parameters (strip_dirnames, print_callees, print_callers) but completely ignores 'module', 'owner', and 'func', leaving their purpose and acceptable values unclear.

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 'Toggle cProfile profiling on/off for a CDV server function.' This is a specific verb+resource pair that distinguishes the tool from its sibling 'get_toggle_cprofile' which likely reads the current state.

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?

The description mentions permission requirement ('Requires sys_viewlogs permission') and explains the toggling behavior, but does not provide guidance on when to use this tool versus checking status via 'get_toggle_cprofile' or other alternative approaches.

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

Deploy Server