Skip to main content
Glama

project_get_page

Retrieves a Loxone Config program page with its blocks, settings, connections, and resolved placeholders so you can inspect logic without missing linked values.

Instructions

Shows one program page: its blocks, their settings and connections, with placeholders resolved.

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": {
      "page": "<page>"
    },
    "name": "project_get_page"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageYes
include_unconnectedNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.9.0

TDQS

B3.1/5.0
Behavior3/5

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

With no annotations, the description must carry the behavioral load, and it does add one genuinely useful detail: placeholders are resolved in the returned data. It still omits read-only confirmation, whether an open project is required, and how large or nested the returned page can be.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One tight, front-loaded sentence with no filler; the scope and the placeholder behavior are packed into a single clause.

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?

No output schema and no annotations mean the description is the only source of truth, and it stops short of the identifier format and return shape. Adequate to recognize the tool's role, not adequate to invoke it confidently on the first attempt.

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% and the description explains neither parameter. The critical ambiguity — whether "page" is a path, ID, or display name — is left for the agent to guess, and the include_unconnected flag is never mentioned, even though it visibly changes what blocks/connections appear.

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?

States a concrete verb and resource ("Shows one program page") and enumerates the payload: blocks, their settings, and connections. This is distinguishable from a single-block getter like project_get_block and from a page lister, though no sibling is named explicitly.

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?

There is no when-to-use guidance, no mention of prerequisites (e.g., whether the project must be open first), and no routing to alternatives such as project_get_block when only one block is needed. Usage is only inferable from the name and the word "Shows".

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