Skip to main content
Glama

structure_list

Lists all rooms or categories with their assignment counts, helping you inspect a Loxone Config project's structure by kind before analyzing or editing pages and blocks.

Instructions

Lists all rooms (kind='raum') or categories (kind='kategorie') with their number of assignments.

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": {
      "kind": "<kind>"
    },
    "name": "structure_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.9.0

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full disclosure burden. It does convey useful behavior beyond the schema by stating that each returned entry carries its number of assignments, but it omits that the call is a safe read, whether results are paginated, and any auth/scope constraints.

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; the value examples are placed inline where they are needed. Nothing could be cut without losing information.

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

Completeness4/5

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

For a one-parameter list tool with no output schema, the description covers what is enumerated and what each entry includes. Only minor gaps remain (pagination, ordering, invalid kind handling) for an agent to call it correctly.

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 coverage is 0% and the schema defines `kind` only as a bare string with no enum, so the description is the sole source of meaning — and it supplies both accepted values ('raum', 'kategorie'), which materially improves correct invocation. It stops short of noting case sensitivity or invalid-value behavior.

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 specific verb (lists) and resource (rooms or categories), and names the discriminator values. An agent can tell this is a read/list tool, distinct from mutating siblings like structure_reassign and structure_remove, 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 Guidelines3/5

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

Usage is implied by 'lists all rooms ... or categories' — the natural read-side counterpart to structure_reassign/structure_remove — but there is no explicit when-to-use, when-not, or prerequisite guidance.

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