Skip to main content
Glama

project_get_block

Inspect a single Loxone Config block to review its connectors, set values, sources, targets, and any settings that differ from defaults.

Instructions

Shows one block in detail: connectors, set values, sources and targets, and values that deviate from the usual defaults.

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": {
      "block": "<block>"
    },
    "name": "project_get_block"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNo
blockYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.9.0

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations, the description carries the behavioral burden. “Shows” indicates a read-oriented operation, and the enumerated result contents provide useful transparency, but error behavior, identifier resolution, page-default behavior, and the absence of side effects are not explicitly addressed.

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?

The single sentence is compact, front-loaded with the operation, and uses the remainder to list concrete result details. There is no redundant or distracting wording.

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?

The output summary is helpful, especially because there is no output schema, but invocation-critical details remain undocumented. The meaning of block, the role and default behavior of page, and basic lookup or failure behavior are significant gaps even for this relatively simple two-parameter tool.

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 does little to compensate. It implies that block selects a single block but gives no identifier format or examples, and it never explains the page parameter or the effect of leaving page null.

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 clearly states the verb and resource: it shows one block in detail. Listing connectors, set values, sources, targets, and non-default values clarifies the inspection scope, although it does not explicitly differentiate the tool from siblings such as project_get_page or project_find.

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?

Detailed single-block inspection implies when the tool is useful, but there is no explicit guidance about prerequisites or when to choose another tool. In particular, it does not explain whether the caller should first locate a block identifier or when the optional page should be supplied.

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