Skip to main content
Glama

catalog_learn

Learns block types, connectors, and templates from Loxone project files so logic edits are possible. Run once before editing pages or blocks to enable validated changes.

Instructions

Learns block types, connectors and templates from project files (needed once before editing).

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": "catalog_learn"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathsNo
resetNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.9.0

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It does disclose the source (project files) and the prerequisite nature, but it never says this builds/populates internal state, whether it overwrites a previous catalog, whether it is expensive, or what it returns on success or failure.

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?

One front-loaded sentence with no filler; the prerequisite note is placed where it matters. It is efficient, though the brevity edges into under-specification rather than tight 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?

For a prerequisite, state-building tool with two undocumented parameters, no annotations and no output schema, the description leaves key questions open: what gets learned and where, whether a prior catalog is discarded, and what reset does. An agent could invoke it, but not confidently reason about its effects.

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%, so the description must explain both parameters. "From project files" loosely hints that paths point at project files, but the default-null meaning (scan everything?) is unstated, and the reset flag — presumably clearing the learned catalog before re-learning — is never mentioned 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?

"Learns block types, connectors and templates from project files" gives a specific verb plus three named resources, so it is clearly distinct from the sibling read-only lookups catalog_list_types and catalog_get_type. It stops short of naming a sibling as the alternative, which keeps it from 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 Guidelines4/5

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

The parenthetical "needed once before editing" is a concrete when-to-use rule that tells the agent to run this before mutation tools like block_add or block_set_params. There is no when-not guidance, no mention of re-running behavior, and no named alternative.

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