Skip to main content
Glama

block_set_params

Set connector defaults, attributes such as Formula or Title, and the in-app description for a Loxone Config block.

Instructions

Sets connector default values, attributes (e.g. Formula, Title) or the description (name in the app) of a block.

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>",
      "params": "<params>"
    },
    "name": "block_set_params"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNo
blockYes
paramsYes

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 provided, so the description carries the full behavioral burden, and it discloses little. It never says whether 'params' merges with existing values or replaces them, whether attributes not listed are preserved, what permissions are required, or what the tool returns. For a mutation tool operating on a block, the partial-vs-full-update semantics are the single most important missing fact.

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 dense sentence with the resource and the settable facets front-loaded and no filler. The parenthetical clarifications ('e.g. Formula, Title', 'name in the app') each earn their place by disambiguating app terminology.

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?

Given a 3-parameter mutation tool with a free-form nested object, no annotations, and no output schema, the description is too thin. The agent still has no way to determine valid keys for 'params', the role of 'page' versus 'block', or the effect of the write on existing block state.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% and 'params' is an open object (additionalProperties: true), so the description is the only source of meaning for its contents — and it does add real value by naming the kinds of keys expected (connector default values, Formula, Title, description/name). However, 'block' and 'page' are completely unexplained, and no key names or value formats are given for the free-form object beyond two examples.

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 ('Sets') and a specific resource ('connector default values, attributes... or the description of a block'), so an agent knows exactly which facets of a block this mutates. It also implicitly distinguishes itself from narrow siblings like block_set_inverted or block_set_position by naming the fields it covers. It stops short of explicitly naming those siblings as alternatives.

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 when-to-use or when-not-to-use guidance and no reference to alternatives. The enumeration of settable fields hints at scope, but an agent must infer on its own that this is the right tool versus block_set_inverted, block_set_position, or block_set_name-style operations.

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