Skip to main content
Glama

project_analyze

Analyzes a Loxone Config project for errors, cleanup candidates, or improvement suggestions, helping you validate and refine logic changes before editing.

Instructions

Analyses the project: errors, clean-up candidates and improvement suggestions (stufe = fehler | aufraeumen | verbesserung).

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

Input Schema

NameRequiredDescriptionDefault
stufeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.9.0

TDQS

B3.2/5.0
Behavior2/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 and falls short: it does not say whether the tool is read-only or mutates project state ("clean-up candidates" could imply either, and a destructive project_discard sibling exists), nor whether analysis is expensive, requires the project to be open, or what the report looks like.

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 front-loaded sentence that states the resource and the three result categories with no filler. The parenthetical carrying the enum values is compact, though cramming parameter values into the purpose sentence slightly blurs structure.

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 one-optional-parameter tool with no output schema and no annotations, the description adequately covers intent but omits read-only vs mutating behavior and output shape, and does not position the tool against the lint/validate/trace siblings that agents would otherwise need to choose between.

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

Parameters3/5

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

Schema coverage is 0% and the schema declares stufe only as an untyped string/null with no enum, so the description's list of allowed values (fehler | aufraeumen | verbesserung) is genuinely additive. However, it does not explain what each mode returns or what the null default means, leaving the parameter only half-specified.

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 names a specific verb and resource ("Analyses the project") and enumerates the three analysis outputs: errors, clean-up candidates, improvement suggestions. It is clear what the tool does, but it never distinguishes itself from siblings such as project_lint or project_validate, which plausibly overlap with the 'errors' mode.

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 stufe values imply that the agent picks a mode, which is a form of usage guidance, but there is no statement of when to prefer project_analyze over project_lint/project_validate, and no indication of what happens when stufe is omitted despite its null default.

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