Skip to main content
Glama

project_open

Open a Loxone project file read-only to get an overview of title, version, pages, and common block types; optionally compare it with the last Miniserver backup and Config autosave.

Instructions

Opens a Loxone project file for reading and returns an overview (title, version, pages, most common block types). Without a path, the newest file of the main project is used (see project_set_main); a bare file name is looked up in the project folder. The field 'abgleich' compares it with the last Miniserver backup and the Loxone Config autosave. The file is never modified.

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

Input Schema

NameRequiredDescriptionDefault
pathNo

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, the description carries the full burden and does well: it declares 'The file is never modified', explains default path resolution (newest file of the main project), the bare-filename lookup rule, and the 'abgleich' comparison against the last Miniserver backup and Config autosave. Gaps remain on failure modes (missing file, unreadable project) and whether opening establishes active project state for sibling tools.

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?

Four compact sentences, front-loaded with the purpose and return contents, then defaults, then the read-only guarantee. The 'abgleich' sentence introduces an unexplained German term, which costs a little clarity but the sentence still earns its place by documenting a return field.

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 single-optional-parameter read tool with no output schema, the description covers return contents and path resolution well. It omits whether an opened project becomes the active context for siblings like project_get_block or project_save, and says nothing about error behavior, which are the main things an agent would still need to guess.

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 compensate, and it largely does: the single optional 'path' parameter is explained in three cases — omitted (newest file of main project), bare filename (looked up in the project folder), and presumably full path. It stops short of stating whether relative or absolute paths are accepted or what happens when the resolved file does not exist.

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 verb and resource ('Opens a Loxone project file for reading') and enumerates what the overview contains (title, version, pages, most common block types), which distinguishes it from pure listing tools like project_list_files. It does not explicitly contrast itself with project_analyze or project_validate, so an agent still has to infer when this overview is sufficient versus a deeper analysis.

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?

Usage is implied rather than stated: the tool is the entry point for reading a project, and project_set_main is referenced only as background for the default-path behavior. There is no explicit 'use this before X' or 'use project_analyze instead when you need Y' guidance despite several plausible sibling alternatives.

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