Skip to main content
Glama

project_set_main

Define which Loxone project files are treated as the main project using a filename pattern, so opening without a path selects the newest match. Omit the pattern to view the current setting.

Instructions

Defines which files belong to the main project (pattern with , e.g. 'my_home_v.Loxone'). project_open without a path then opens the newest matching file. Without pattern: show the current setting.

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_set_main"
  }
}

Input Schema

NameRequiredDescriptionDefault
patternNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.9.0

TDQS

A4.1/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It does disclose that this persists a configuration that changes project_open's behavior and that the no-argument call is a read. It omits what happens with an invalid pattern, whether the setting survives restarts, and what the current-setting read returns.

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?

Three short sentences, front-loaded with the core purpose, then the consumer behavior, then the read mode. Nothing is redundant or padded.

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 settings tool this is close to sufficient, and the config-to-project_open linkage is valuable context. The gap is the return value of the read mode and error behavior, which are covered by neither an output schema nor the description.

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 description coverage is 0%, so the description must compensate, and it does: it explains that the value is a glob-style pattern using '*', supplies a concrete example ('my_home_v*.Loxone'), and defines the null/omitted case as a read. Validation rules and default-extension behavior remain unstated.

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 and resource ('Defines which files belong to the main project') and adds the effect on a named sibling: project_open without a path opens the newest matching file. An agent can tell it apart from project_open and project_list_files without opening any schema.

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?

Gives concrete context for both modes: supply a pattern to set the main project, omit it to show the current setting. It also explains the downstream consequence via project_open. No explicit 'when not to use' or error-case guidance, 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.