Skip to main content
Glama
Sign In
Cloudera Data Visualization MCP Server

Cloudera Data Visualization MCP Server

by kevintalbert
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

set_gc_monitor

Enable or disable garbage collection monitoring on the Cloudera Data Visualization server to control performance tracking.

Instructions

Enable or disable GC monitoring on the CDV server.

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": {
      "enabled": "<enabled>"
    },
    "name": "set_gc_monitor"
  }
}

Input Schema

NameRequiredDescriptionDefault
enabledYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior2/5

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

With no annotations, the description carries full burden but only says 'Enable or disable GC monitoring.' It does not disclose behavioral traits such as reversibility, performance impact, authentication requirements, or what happens to ongoing monitoring.

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 a single, efficient sentence that is front-loaded with key information. No unnecessary words.

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 toggle tool with one parameter and an output schema, the description is minimally adequate. It covers the core purpose but lacks any explanation of output, behavior, or best practices.

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 single boolean parameter 'enabled' is explained implicitly by the description ('Enable or disable'). With 0% schema description coverage, the description adds minimal meaning beyond the schema's type and requirement.

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 'Enable or disable GC monitoring on the CDV server,' specifying the action and resource. It distinguishes from sibling tools like get_gc_monitor (retrieve state) and get_gc_stats (get statistics).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance is provided on when to use this tool versus alternatives. There is no discussion of prerequisites, side effects, or context for enabling/disabling GC monitoring.

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

Deploy Server

Other Tools