Skip to main content
Glama

page_add

Adds a new empty program page after the last existing page, optionally assigning a room and category to organize Loxone Config project pages.

Instructions

Adds a new, empty program page (after the last page), optionally with room and category.

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": {
      "title": "<title>"
    },
    "name": "page_add"
  }
}

Input Schema

NameRequiredDescriptionDefault
roomNo
titleYes
categoryNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.9.0

TDQS

C2.8/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full burden. It discloses that the page is created empty and appended at the end, but says nothing about side effects, whether a project must be loaded, permissions, or what handle/identifier comes back (critical, since block_add presumably needs a page reference).

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?

A single front-loaded sentence with the verb, resource, ordering behavior, and optional inputs; no wasted words or filler.

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?

For a creation tool with no annotations, no output schema, and zero parameter documentation, the description is thin. An agent still cannot tell what the call returns, whether the title must be unique, or how to reference the new page afterward.

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?

With 0% schema description coverage, the description must compensate and largely does not. It names room and category as optional but never explains what they mean or what values are valid, and the required title parameter is not addressed at all.

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?

Specific verb and resource ("Adds a new, empty program page") plus placement semantics ("after the last page") and the fact that room/category are optional. It is clearly distinguishable from siblings like block_add or page_get, but it does not explicitly name or rule out any alternative.

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 statement that a page must exist before blocks can be added, no prerequisite about an open project, and no mention of any alternative sibling. The ordering hint ("after the last page") is the only contextual cue.

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