Kura MCP Server

kura_create_snapshot

Create a configuration snapshot for an Eclipse Kura IoT gateway instance to capture its current settings, enabling backup or rollback.

Instructions

Create a configuration snapshot

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_create_snapshot"
  }
}

Input Schema

Name	Required	Description	Default
`instance`	Yes	Kura instance name

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 2, 2026

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 carries the full burden. It only says 'create,' which implies a write operation, but does not disclose any side effects, permission requirements, or whether snapshots are destructive. This is minimal information for a mutating tool.

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

Conciseness4/5

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

The description is a single short sentence, which is concise but minimal. It could include more useful context while remaining brief, but it does communicate the core purpose.

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?

With only one parameter fully described by the schema and no output schema, the description still lacks behavioral and usage context. It does not mention when to use the tool or any effects, making it incomplete for an agent deciding how to invoke it.

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 covers the only parameter, 'instance,' with a description and enum (LOCAL). The description adds no parameter-specific information, but the schema already fully documents it, so baseline 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 states 'Create a configuration snapshot,' which clearly identifies the action and resource. It distinguishes from siblings like kura_get_snapshots and kura_rollback_snapshot by being the create operation. However, it lacks any additional context about what a snapshot contains or its scope.

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. There is no mention of prerequisites, such as making a snapshot before updates, or exclusions compared to other snapshot-related tools.

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

Deploy Server