Skip to main content
Glama
fieldpuppet

fieldpuppet

Official

Load a saved project

load_project
Destructive

Starts the simulated devices from a saved project on their recorded ports, optionally removing running devices first with replace, so you can resume a Modbus test setup without reconfiguring it.

Instructions

Start the devices stored in a project saved earlier with save_project, on the ports recorded in it. By default they are added next to the devices already running, and the call fails part-way if an id or port is already in use (devices started before the failure keep running). With replace true, all running devices are removed first, which discards their unsaved state. Call list_projects to see the available names. Returns the devices that were started.

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

Input Schema

NameRequiredDescriptionDefault
nameYesName of a saved project, exactly as shown by list_projects.
replaceNotrue: remove all currently running devices before loading. Default false: keep them.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.1.2
    • addedInput schema / properties / name / description
      Added value: +"Name of a saved project, exactly as shown by list_projects."
    • changedInput schema / properties / replace / description
      Previous value: -"Remove the currently running devices first. Default false."New value: +"true: remove all currently running devices before loading. Default false: keep them."
  2. First observedv0.1.1

TDQS

A4.7/5.0
Behavior5/5

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

Goes well beyond the annotations by disclosing partial-failure semantics ("the call fails part-way if an id or port is already in use (devices started before the failure keep running)") and the consequence of replace ("discards their unsaved state"), which the destructiveHint alone would not convey.

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?

Four tight sentences in a sensible order: what it does, default behavior and failure mode, destructive alternative, prerequisite lookup, return value. No padding.

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?

For a two-parameter, non-idempotent, destructive loader with no output schema, the description covers scope, collision behavior, destructive option, input source, and return value ("Returns the devices that were started"). Nothing an agent needs is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so 3 is the baseline; the description earns more by explaining what replace=true actually costs (unsaved state of running devices is lost) and by clarifying the port/id collision behavior tied to the name parameter.

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 concrete verb and resource ("Start the devices stored in a project") and ties the input to its producer ("saved earlier with save_project"), so the agent can place it among save_project/list_projects without opening the schema.

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

Usage Guidelines4/5

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

Gives the default (add alongside running devices) and the explicit condition for the alternative ("With replace true..."), plus a prerequisite pointer to list_projects for valid names. It stops short of naming an alternative route such as remove_all_devices followed by a manual rebuild.

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