Skip to main content
Glama

sync_check

Compares the project file, Loxone Config autosave, and Miniserver program to detect differences before editing. Use it before every change to verify synchronization.

Instructions

Compares project file, Loxone Config autosave and Miniserver program (pass miniserver_xml_path, e.g. the Miniserver-Backup file, for a content comparison). Call before every change.

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

Input Schema

NameRequiredDescriptionDefault
ask_miniserverNo
miniserver_xml_pathNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.9.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations provided, the description must carry the full behavioral burden. It usefully discloses the comparison targets and a conditional content-comparison mode via miniserver_xml_path, but it does not clarify whether the tool mutates state, what it returns, how ask_miniserver affects behavior, or what permissions are required.

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?

The definition is a single front-loaded sentence with no wasted wording. The parenthetical example adds concrete value without disrupting the main comparison statement.

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 two-parameter comparison tool with no annotations and no output schema, the description covers the purpose and one parameter well. It remains incomplete because ask_miniserver is unexplained and no behavioral context is given about safety, results, or side effects.

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

Parameters2/5

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

Schema description coverage is 0%, so the description needs to explain both parameters. It gives useful meaning for miniserver_xml_path, including an example and the effect of triggering a content comparison, but it completely omits ask_miniserver, leaving one of the two parameters undocumented.

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, "Compares," and names the three artifacts being compared: project file, Loxone Config autosave, and Miniserver program. It is clear what the tool does, but it does not explicitly distinguish itself from possible sibling tools such as project_analyze or project_changes.

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?

The phrase "Call before every change" gives a concrete when-to-use rule, which is strong guidance for a preflight check. However, it does not state when not to use the tool or name alternative tools for related comparison tasks.

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