Skip to main content
Glama

project_text

Read a readable text view of a Loxone Config project or a single page, showing blocks, settings, inputs, and peripheral outputs for inspection.

Instructions

Readable text view of the program (or working copy): per page the blocks with settings and inputs ('I1 <- Source.Output') and the outputs to peripherals. Without page: whole project (long).

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

Input Schema

NameRequiredDescriptionDefault
pageNo

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 burden. It discloses that output is human-readable text with block settings/inputs and peripheral outputs, and warns that whole-project output is long. However, it does not explicitly confirm read-only behavior, permissions, or error handling.

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 definition is a single dense sentence with a parenthetical example and a scope caveat. It is front-loaded and mostly earns its place, though the quoted input/output example is somewhat compressed.

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-parameter read tool with no annotations or output schema, it explains the returned content and page scoping. It omits page format details, an explicit read-only guarantee, and error behavior, so it is adequate but not fully complete.

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%, and the only parameter has no schema description. The description compensates by explaining the page parameter's effect: per-page output when supplied, entire project when omitted, plus the 'long' caveat. That adds meaningful semantics beyond the bare 'page' field.

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 identifies a specific read operation ('Readable text view of the program') and clarifies scope: per-page output versus whole-project output. It does not explicitly differentiate from sibling read tools such as project_get_page 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 Guidelines3/5

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

It gives a scoping hint: supply page for per-page output, omit it for the whole project with a 'long' warning. It does not state when to choose this over sibling read tools or list exclusions, leaving alternatives to inference.

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