Skip to main content
Glama

io_set_statistics

Enable or disable statistics for an analog input or memory block, recording every change or accumulated values as Loxone Config does for measurements.

Instructions

Enables statistics for an analog input or memory (on every change, accumulated - as Loxone Config does for measurements) or disables it.

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

Input Schema

NameRequiredDescriptionDefault
blockYes
enabledNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.9.0

TDQS

C2.9/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 behavioral burden. It does explain the accumulation semantics ('on every change, accumulated'), which is genuinely useful, but it says nothing about whether disabling destroys previously accumulated data, what permissions or project state are required, whether the change persists to the controller, or what the call 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?

A single front-loaded sentence with the verb first and no filler. The nested parenthetical ('on every change, accumulated - as Loxone Config does for measurements') is slightly convoluted but does carry real semantic content rather than padding.

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?

With no annotations, no output schema, and zero schema description coverage on two parameters, the description is the only source of truth and is too thin. An agent still cannot tell how to identify the target block or what side effects accompany disabling statistics, which are the two things it most needs before calling.

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% for both parameters, so the description must compensate and largely does not. 'Analog input or memory' hints at what 'block' accepts but never says it is a block identifier/reference, and 'or disables it' only obliquely maps to the 'enabled' boolean, without clarifying that enabled=false is the disable path or that the default is true.

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 gives a specific verb (enables/disables) and a specific effect (statistics on an analog input or memory), which tells an agent exactly what the tool does and which block types it applies to. It does not name or contrast any sibling, but none of the listed siblings appear to cover statistics, so the purpose remains unambiguous.

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 rather than stated: the mention of 'analog input or memory' signals the applicable block types, and 'as Loxone Config does for measurements' gives a rough scenario. There is no explicit when-to-use / when-not-to-use guidance, no prerequisites, and no statement about what happens if the tool is applied to an unsupported block type.

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