Cloudera Data Visualization MCP Server

get_toggle_cprofile

Check if cProfile profiling is enabled for a Cloudera Data Visualization server function. Specify module, owner, or function to inspect specific profiles.

Instructions

Check whether cProfile profiling is enabled for a CDV server function. Defaults to sqlrun.views_jsonselect / jsonselect_parallel if not specified.

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

Input Schema

Name	Required	Description	Default
`module`	No
`owner`	No
`func`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0May 26, 2026

TDQS

A3.6/5.0

Behavior3/5

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

With no annotations provided, the description carries full burden. It reveals the tool checks enabling status and defaults to specific functions, but fails to explicitly state that it is read-only or describe permissions, rate limits, or output format. Adequate but lacking explicit behavioral details.

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?

Two concise sentences, front-loaded with the core purpose. No unnecessary words or repetition. Efficiently communicates the main function and default behavior.

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?

Given 3 parameters with no schema descriptions and no annotations, the description should be more complete. It lacks indication of output (likely boolean) and does not frame the operation as read-only. However, the presence of an output schema reduces the burden slightly. Completeness is average.

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?

Input schema has 0% description coverage, so the description must compensate. It mentions a default function but does not explain the meaning of each parameter (module, owner, func) individually, leaving mapping unclear. Minimal additional value beyond schema names.

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 tool checks whether cProfile profiling is enabled for a CDV server function, with a specific verb ('check') and resource ('profiling enabled status'). It also mentions default functions, distinguishing it from other 'get' tools that retrieve data objects.

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 implies usage for checking profiling status but does not explicitly state when to use this tool versus its counterpart 'toggle_cprofile' or other tools. No exclusions or alternatives are mentioned, leaving the agent to infer context.

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

Deploy Server