Skip to main content
Glama

project_changes

Lists all differences between the working copy and the opened Loxone project file, including added or removed blocks, connections, and value changes.

Instructions

Lists all changes of the working copy compared with the opened file (new/removed blocks, connections, values).

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

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?

With no annotations, the description carries the full disclosure burden. It usefully states the comparison baseline (working copy vs the opened file) and what kinds of deltas are reported (new/removed blocks, connections, values), which implies a non-mutating inspection. It does not state that there are no side effects, whether an open project/document is required, or what the result 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 with no filler, and the parenthetical enumeration is efficient. The phrase "compared with the opened file" is slightly ambiguous about what exactly is on each side of the diff.

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 zero-parameter tool with no output schema, the description should say enough about the returned structure; it lists the kinds of changes but not the shape or granularity of the result. Missing prerequisites (must a project/file be open?) leave a real gap relative to how the tool would be invoked.

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 takes zero parameters, so the baseline is 4; there is nothing about arguments that the description needs to explain.

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?

Names a specific verb ("Lists") plus a well-scoped resource ("all changes of the working copy compared with the opened file") and enumerates the change categories in parentheses. An agent can tell this is a diff-inspection tool, though it never contrasts itself with siblings like project_discard or project_undo.

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 only implied: the comparison against "the opened file" hints this is for reviewing unsaved pending edits. There is no explicit statement of when to call it (e.g. before project_save) or which sibling to use to revert changes instead, so the agent must infer.

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