Cloudera Data Visualization MCP Server

create_connection

Create a new data connection to a target data source in Cloudera Data Visualization. Verify no existing connection matches before calling.

Instructions

Create a new CDV data connection.

IMPORTANT: Do NOT call this without first calling list_connections() and confirming with the user that no existing connection points to their target data source.

body fields: name (str), type (str), connection_info (object with host, port, etc.).

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": {
      "body": "<body>"
    },
    "name": "create_connection"
  }
}

Input Schema

Name	Required	Description	Default
`body`	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.2/5.0

Behavior3/5

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

No annotations provided, so description must disclose behavioral traits. It implies mutation (creation) and warns about checking for existing connections, but does not detail side effects like overwrite behavior, error handling, or authentication requirements. Partial 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?

The description is very concise, using three short sentences. Important warnings are front-loaded with uppercase emphasis. Every sentence provides value without redundancy.

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 that an output schema exists, description does not need return values. It covers purpose, usage guidelines, and parameter hints. Lacks details on error cases or idempotency, but is largely complete for a creation tool with a safety warning.

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 coverage is 0% with only a generic 'body' object. The description adds meaning by listing fields (name, type, connection_info) and hints at structure, which compensates partially. However, it is not exhaustive and lacks constraints or required fields.

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 states 'Create a new CDV data connection' which clearly identifies the verb and resource. It distinguishes from sibling create_* tools by specifying 'connection' and adds context about CDV. The body fields hint further clarifies the purpose.

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

Usage Guidelines5/5

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

Explicitly instructs to first call list_connections() and confirm with user that no existing connection targets the data source. This provides clear when-to-use and when-not-to-use guidance, including a prerequisite step.

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

Deploy Server