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

Cloudera Data Visualization MCP Server

by kevintalbert
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

import_migration

Imports a Cloudera Data Visualization migration bundle by associating it with a data connection, with an optional validation step.

Instructions

Import a CDV migration bundle.

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": {
      "dataconnection_name": "<dataconnection_name>"
    },
    "name": "import_migration"
  }
}

Input Schema

NameRequiredDescriptionDefault
dataconnection_nameYesName of the data connection to associate imported artifacts with.
json_dataNoStringified JSON migration payload.
sanity_checkNoRun validation before import (default True).

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/5.0
Behavior1/5

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

No annotations exist, and the description does not disclose behavioral traits such as whether the import is destructive, requires specific permissions, or has side effects. This leaves the agent blind to important context.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single short sentence, which is under-specified for a complex import operation. While concise, it lacks necessary details and structure to be helpful.

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 complexity of a migration import and the lack of annotations, the description fails to provide sufficient context. It does not explain validation, error behavior, or return value, leaving critical gaps.

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 100%, so the description does not need to explain parameters much. However, it adds no additional context beyond the schema, such as the expected format of json_data or the effect of sanity_check.

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 (import) and the object (CDV migration bundle), distinguishing it from its sibling export_migration. It is specific and unambiguous.

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 vs alternatives (e.g., export_migration), nor any prerequisites or conditions. The agent gets no context for decision-making.

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