Kura MCP Server

kura_connect_cloud

Connect a cloud connection on an Eclipse Kura gateway by specifying the instance and cloud connection PID to establish connectivity.

Instructions

Connect a cloud connection

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": {
      "instance": "<instance>",
      "pid": "<pid>"
    },
    "name": "kura_connect_cloud"
  }
}

Input Schema

Name	Required	Description	Default
`pid`	Yes	Cloud connection PID
`instance`	Yes	Kura instance name

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 2, 2026

TDQS

D1.7/5.0

Behavior1/5

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

With no annotations, the description carries the full burden of behavioral disclosure. It does not mention side effects, whether a network connection is established, authentication requirements, or what happens if the connection already exists. The tool appears to be a mutating operation, but no behavioral details are shared.

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 extremely short, but this is under-specification rather than conciseness. It fails to provide any meaningful information beyond the tool name. Every sentence should earn its place; this one does not.

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

Completeness1/5

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

The tool performs a connection action that likely has side effects and requires context. There is no output schema, no annotations, and no explanation of expected behavior, return values, or errors. The description is completely inadequate for a tool with this level of complexity.

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 schema descriptions already cover both parameters ('pid' and 'instance') at 100% coverage. The description adds no further meaning to the parameters, so the baseline score of 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Connect a cloud connection' essentially restates the tool name 'kura_connect_cloud' using the same verb and noun. It lacks specificity about what connecting a cloud connection entails and does not differentiate from sibling tools like kura_disconnect_cloud or kura_get_cloud_connections.

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

Usage Guidelines1/5

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

There is no guidance on when to use this tool versus alternatives. No mention of prerequisites, conditions, or exclusions is provided. The description gives no context for selecting this tool over its siblings.

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

Deploy Server