Skip to main content
Glama

project_lint

Validates Loxone project or working copy before loading to catch silent errors like invalid placeholder outputs, dangling connections, missing targets, out-of-sheet blocks, overlaps, and malformed titles.

Instructions

Pre-load check of the whole project (or working copy): errors Loxone Config drops silently (invalid placeholder outputs, dangling connections, placeholders without target) plus blocks outside the sheet, overlaps, titles with < or %, placeholders without connection.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

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?

No annotations are provided, so the description carries the full behavioral burden. It helpfully discloses the specific categories of errors checked, such as silently dropped errors and blocks outside the sheet, but it does not say whether the operation is read-only, whether it modifies the project, or what happens when issues are found.

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?

The description is a single front-loaded sentence that immediately states the core purpose before listing checks. It is dense but every clause contributes specific information, with 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?

There is no output schema and no annotations, so the description should ideally explain what the tool returns or how issues are surfaced. It thoroughly describes what is checked, but leaves the result format and relationship to project_validate unstated.

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?

The tool has zero parameters, so the baseline score is 4. The description adds no parameter semantics because none are needed, and the schema already has 100% coverage.

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 uses a specific verb-and-resource phrase, 'Pre-load check of the whole project (or working copy),' and enumerates the exact problems it detects. It is clear what the tool does, but it does not explicitly distinguish itself from the sibling tool project_validate.

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 phrase 'Pre-load check' implies this is used before loading a project, giving some contextual usage guidance. However, it does not state when to use this instead of project_validate or project_analyze, nor does it mention exclusions or alternatives.

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