Skip to main content
Glama
fieldpuppet

fieldpuppet

Official

Save devices to a project

save_project
DestructiveIdempotent

Save all running devices to a named project file for later restoration. Overwrites existing projects with the same name; fails if no devices are running.

Instructions

Save every running device (points, current values, signals, ports, running scenarios) to a named project file on this machine so the same setup can be restored later with load_project. An existing project with the same name is overwritten without warning; call list_projects first to check. Running devices are not affected. Traffic logs and active faults are not saved. Fails if no devices are running. Returns the file path and device count.

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": "save_project"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesProject name: letters, digits, '-' and '_', at most 64 characters.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.1.2
    • changedInput schema / properties / name / description
      Previous value: -"Letters, digits, '-' and '_'."New value: +"Project name: letters, digits, '-' and '_', at most 64 characters."
  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 (destructiveHint=true, idempotentHint=true) by naming exactly what is destroyed (a same-named project, without warning) and what is excluded (traffic logs, active faults). It also discloses side-effect scope (running devices unaffected), the failure condition, and the return payload, which is exactly the context an agent needs for a destructive write.

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 short sentences, front-loaded with the action, then destruction warning, then side effects/exclusions, then return value. No filler, and the most decision-relevant fact (silent overwrite) is placed early.

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 one-parameter destructive tool with no output schema, everything needed is present: precondition, overwrite risk, unaffected state, excluded data, and the shape of the return value (file path and device count). No gaps remain that would cause a misinvocation.

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% and the single 'name' parameter already documents allowed characters and length, so the heavy lifting is done structurally. The description adds only that the name maps to a file 'on this machine', which is helpful context but not a meaningful semantics expansion 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 (save) and resource (running devices to a named project file) and pins the scope precisely, including what 'every running device' means (points, current values, signals, ports, scenarios). It explicitly names load_project as the counterpart operation, so an agent can distinguish it from siblings without opening a 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?

Gives explicit routing guidance: call list_projects first because an existing project is overwritten without warning, and use load_project to restore. It also states the precondition (fails if no devices are running), which tells the agent when this tool is not usable.

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