Skip to main content
Glama

project_trace

Traces signal flow forward or backward through Loxone logic across placeholders and pages to reveal dependencies and support debugging.

Instructions

Follows a signal forwards or backwards through the logic (across placeholders and pages).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "block": "<block>"
    },
    "name": "project_trace"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNo
blockYes
connectorNo
directionNoforward
max_depthNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.9.0

TDQS

C2.7/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden. It does not state whether the operation is read-only, what side effects or permissions are involved, what the return shape is, or how max_depth affects traversal; it only names the traversal concept.

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 single sentence is front-loaded and free of unnecessary wording. It is concise, though its brevity contributes to the under-specification captured in contextual completeness.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

This is a traversal tool with five parameters, no annotations, no output schema, and no schema parameter descriptions. A one-sentence description cannot adequately convey traversal semantics, parameter roles, return values, or failure modes.

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

Parameters2/5

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

Schema description coverage is 0% across five parameters. The description vaguely maps 'forwards or backwards' to direction and 'pages' to page, but it does not explain block vs. connector, the required block parameter, the default direction, or max_depth.

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 ('Follows') and resource ('signal') and adds scope ('across placeholders and pages'), making the core operation clear. It does not distinguish this tool from siblings like project_find or project_analyze, so it stops short of a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description mentions forward/backward traversal but gives no guidance on when to use this tool instead of alternatives such as project_find or project_get_block. There are no preconditions, exclusions, or contextual cues to help an agent select it correctly.

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