Skip to main content
Glama

verify_load

Verifies a Miniserver load by waiting for response, backing up the running program via Git, and comparing it to the expected project file; cleanup moves old versions to recycle bin.

Instructions

Call after loading a file into the Miniserver with Loxone Config: waits until the Miniserver answers again (up to 3 min), backs up the running program (Git) and compares it with the expected project file (default: newest file of the main project). cleanup=True moves older versions of the main project to the recycle bin on success.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "verify_load"
  }
}

Input Schema

NameRequiredDescriptionDefault
fileNo
cleanupNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.9.0

TDQS

A3.9/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 behavioral burden well: it discloses the up-to-3-minute blocking wait, a Git backup side effect, a comparison step, and that cleanup moves older project versions to the recycle bin (i.e. recoverable, not permanent deletion). It omits what happens on timeout or comparison mismatch, which is the main remaining gap.

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?

A single dense sentence, but it is front-loaded with the triggering condition and then layers on timing, side effects, and the parameter note in a logical order. Nothing reads as padding, though splitting the cleanup clause out would improve scanability.

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 tool whose core output is a comparison verdict, the description never says what the result looks like or how a mismatch is reported, and there is no output schema to fill that in. Timing and side-effect coverage are good, but the verification outcome is the missing piece.

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 0%, so the description must define the parameters and it largely does: cleanup=True is explained including its default-off implication and its effect, and file is defined as the expected project file with the null default resolving to the newest file of the main project. The accepted format of file (path vs. name) is still unstated.

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?

States a specific action chain: wait for the Miniserver to answer, back up the running program via Git, and compare it to the expected project file. This clearly distinguishes it from a plain backup tool like backup_miniserver, though it never names a sibling explicitly.

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?

"Call after loading a file into the Miniserver with Loxone Config" gives a precise triggering condition, so the agent knows exactly when this tool applies. It does not state when not to use it or which sibling to prefer instead, which keeps it short of a 5.

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