Skip to main content
Glama
fieldpuppet

fieldpuppet

Official

Clone a device many times

clone_device

Create multiple independent copies of a running simulated device on separate ports for load testing, each preserving the source’s points, values, signals, and settings at copy time.

Instructions

Create several copies of a running device, each on its own port, for example 50 identical meters for a load test. Copies start with the source's points, current values, signals and settings; later changes to the source do not reach them. Use create_device for a single new device. If a copy cannot be created the call stops there and the error says how many were made; those copies keep running. Returns the id, port and unit id of every copy.

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": {
      "source_id": "<source_id>",
      "count": "<count>"
    },
    "name": "clone_device"
  }
}

Input Schema

NameRequiredDescriptionDefault
countYesHow many copies to create.
id_prefixNoCopies are named <prefix>-1, <prefix>-2, ... Default: the source id.
source_idYesId of the running device to copy.
start_portNoPort of the first copy; the others use the following ports. Omit for the next free ports.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv0.1.2
    • addedInput schema / properties / count / description
      Added value: +"How many copies to create."
    • changedInput schema / properties / id_prefix / description
      Previous value: -"Optional id prefix; copies are named <prefix>-1, <prefix>-2, ..."New value: +"Copies are named <prefix>-1, <prefix>-2, ... Default: the source id."
    • changedInput schema / properties / source_id / description
      Previous value: -"Device id as returned by create_device or list_devices."New value: +"Id of the running device to copy."
    • changedInput schema / properties / start_port / description
      Previous value: -"Optional first port; copies use consecutive ports. Omit for the next free ports."New value: +"Port of the first copy; the others use the following ports. Omit for the next free ports."
  2. First observedv0.1.1

TDQS

A4.6/5.0
Behavior5/5

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

Adds substantial behavior beyond the annotations: copies are snapshots that do not receive later source changes, and on partial failure the call stops with an error reporting how many copies were made while those copies keep running. Those two facts — snapshot isolation and partial-failure persistence — are exactly what an agent needs and are not derivable from the hints.

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?

Four tight sentences, front-loaded with the core action and followed by snapshot semantics, the sibling contrast, and failure behavior — each sentence earns its place. Slightly dense, but no waste.

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

Completeness5/5

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

With no output schema, the description supplies the return shape (id, port and unit id of every copy) and covers scaling limits implicitly via example. Nothing an agent needs to invoke it correctly is missing.

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 all four parameters (including start_port and id_prefix) are already documented in structured form. The description only reinforces the port convention ('each on its own port') and the returned unit id, adding little per-parameter meaning beyond the schema.

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?

States a specific verb and resource ('Create several copies of a running device, each on its own port') and grounds it with a concrete example (50 identical meters for a load test). It explicitly contrasts with create_device, so the agent can distinguish it from the nearest sibling without opening either schema.

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

Usage Guidelines5/5

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

Names the alternative ('Use create_device for a single new device') and gives the selecting condition for this tool (many copies, load testing). The routing decision is fully resolved inside the description.

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