Skip to main content
Glama

live_block

Retrieves read-only current values for a Loxone block or device, returning all outputs for large blocks so you can inspect live state.

Instructions

Current value of a block or device; for large blocks all outputs. Read only.

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

Input Schema

NameRequiredDescriptionDefault
pageNo
blockYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.9.0

TDQS

B3/5.0
Behavior3/5

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

With no annotations supplied, the description does carry the safety burden and does so by stating 'Read only,' which tells the agent this is a non-mutating call. It also discloses that large blocks return all outputs, a useful behavioral nuance. It does not address freshness, permissions, failure modes, or the effect of the page parameter.

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?

Two tight clauses, front-loaded with the resource and followed by the large-block caveat and the read-only note. No filler, although the telegraphic phrasing borders on under-specification.

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?

For a simple two-parameter read tool with no output schema, the description covers the return concept (current value, all outputs for large blocks) reasonably well. It falls short on the undocumented page parameter and gives no sense of return shape or error behavior.

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 compensate and it only partially does: 'block' is inferable from the wording, but 'page' is never mentioned at all, and neither parameter's expected format or selection rules are explained.

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?

Conveys a specific operation and resource: retrieve the current value of a block or device, with a caveat that large blocks return all outputs. It is clearly not a historical or mutation tool, though it does not name or distinguish itself from siblings such as live_history or project_get_block.

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 explicit when-to-use guidance and no named alternative. An agent must infer from the word 'Current' that this is a live-state read versus live_history's retrospective read; the definition never states that comparison or any preconditions.

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