Skip to main content
Glama
Sign In
Kura MCP Server

Kura MCP Server

by MMaiero
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

kura_get_cloud_connections

Retrieve all configured cloud connections from a Kura instance to monitor and manage cloud connectivity for IoT gateways.

Instructions

Get all cloud connections from a Kura instance

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>"
    },
    "name": "kura_get_cloud_connections"
  }
}

Input Schema

NameRequiredDescriptionDefault
instanceYesKura instance name

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.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 the full burden for behavioral disclosure. It does not mention that the operation is read-only, whether it returns sensitive data, or any side effects. The absence of such context leaves the agent without insight into safety or prerequisites.

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, front-loaded sentence with no extraneous information. It communicates the essential purpose efficiently.

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?

The tool is simple with one parameter and no output schema, but the description omits context such as the format of cloud connections or whether returned data includes status details. It is minimally adequate for a list-getter but leaves 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% with the 'instance' parameter having a description and an enum. The description adds no additional parameter meaning, so the baseline of 3 applies.

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 uses a specific verb ('get') and resource ('all cloud connections') with a clear scope ('all') and target ('from a Kura instance'). It clearly distinguishes itself from sibling tools like get_configurations or connect_cloud by focusing on a specific resource type.

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 instead of alternatives. The description simply states the function without mentioning that it is read-only, when it should be preferred, or how it relates to connect/disconnect tools.

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