Skip to main content
Glama

project_save

Saves the working copy as a new file in the project folder after validation passes, never overwriting existing files, so you can review and load the validated Loxone Config project yourself.

Instructions

Saves the working copy as a NEW file in the project folder (never overwrites). Validation runs first; with errors nothing is saved. The project timestamp is set to now. Open the new file in Loxone Config, check it and load it into the Miniserver yourself.

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

Input Schema

NameRequiredDescriptionDefault
filenameYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.9.0

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and handles much of it well: it discloses the non-destructive write model (always a new file), the validation gate, the atomic failure behavior ("with errors nothing is saved"), and a side effect (project timestamp set to now). It stops short of stating required permissions, what the project folder is, or what happens if a file with that name already exists.

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, each carrying distinct information: file semantics, validation gate, failure consequence, timestamp side effect, and follow-up steps. The most decision-relevant fact (new file, never overwrites) is front-loaded and there is no filler.

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

Completeness3/5

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

For a mutation tool with no annotations and no output schema, the description covers side effects and failure behavior adequately, but leaves two meaningful gaps: the return value (presumably the new file's path) and the preconditions/permissions needed to save. An agent can invoke it correctly but not fully predict the result shape.

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 0% for the single `filename` parameter, so the description must compensate. The phrase "as a NEW file in the project folder" implies filename names a new file within the project folder, which is real added meaning, but the description never specifies format, extension, or what happens on a name collision.

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 a specific verb and resource ("Saves the working copy") and immediately pins down the key semantics: a NEW file, never an overwrite. It implicitly differs from project_validate by noting validation is an automatic precondition rather than the goal, but it never names a sibling tool explicitly, so an agent must infer the routing.

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

Usage Guidelines3/5

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

The closing sentence ("Open the new file in Loxone Config, check it and load it into the Miniserver yourself") gives useful post-use context and makes clear this tool does not deploy to the Miniserver. However, it never says when NOT to call it (e.g., when to use project_discard or project_validate alone), so usage is implied rather than spelled out.

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