Skip to main content
Glama
Sign In
Kura MCP Server

Kura MCP Server

by MMaiero
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

kura_test_connection

Test connectivity to a specified Kura instance to ensure the REST API is reachable before managing IoT gateway devices.

Instructions

Test connection to 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_test_connection"
  }
}

Input Schema

NameRequiredDescriptionDefault
instanceYesKura instance name

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description bears the full burden of disclosing behavior. 'Test connection' implies a non-destructive probe, but it does not clarify whether the operation has side effects, what happens on failure, or whether it requires prior authentication. This is minimal transparency for a tool that could involve network I/O.

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, concise sentence that delivers the core purpose with no redundant words. It is front-loaded and easy to parse.

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?

The tool is simple (one param, no output schema), but the description lacks critical context about expected results or failure behavior. Since there are no annotations and no output schema, the description should have mentioned what 'test' returns (e.g., success/failure) to be complete.

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 described as 'Kura instance name' and restricted to enum 'LOCAL'. The description does not add any extra meaning beyond the schema, so the baseline of 3 is appropriate.

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

Purpose4/5

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

The description uses the verb 'Test' and the resource 'connection to a Kura instance', making the primary purpose clear. It is distinguished from sibling tools like kura_connect_cloud (which connects to cloud) and other get/update operations. However, it does not specify what 'test' entails (e.g., authentication check, latency probe), so it is not a full 5.

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?

The description provides no guidance on when to use this tool versus alternatives. It does not mention using it before other Kura operations or contrast it with kura_connect_cloud/kura_disconnect_cloud. There is no 'when' or 'when not to use' information.

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