Skip to main content
Glama
STREONOR MCP

STREONOR MCP

by lde-medeiros

apply_action_change

Destructive

Apply a previewed action or icon edit with backup to update STREONOR scenes, keypads, or app configurations.

Instructions

Apply a previewed action/icon edit with backup. manage_app=True closes and reopens STREONOR. force_close=True can discard unsaved app edits. Use live_scene_name on Windows to import the edit into a new scene while STREONOR runs. Use live_in_place=True to set or reset a keypad or Scene Shift icon state in the selected single-page S6 Mini scene on Windows. Imported icons become 1254 x 1254 PNG.

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": {
      "profile": "<profile>",
      "operation": "<operation>",
      "coordinate": "<coordinate>",
      "expected_sha256": "<expected_sha256>"
    },
    "name": "apply_action_change"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNo
hotkeyNo
profileYes
auto_iconNo
operationYes
controllerNoKeypad
coordinateYes
flow_stepsNo
flow_titleNo
icon_queryNo
image_pathNo
manage_appNo
action_nameNo
force_closeNo
state_indexNo
state_imagesNo
live_in_placeNo
action_settingsNo
expected_sha256Yes
live_scene_nameNo
source_coordinateNo
expected_image_sha256No
expected_auto_icon_sha256No
expected_state_image_sha256No

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.8.2

TDQS

B3.3/5.0
Behavior4/5

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

Annotations already flag this as destructive and not read-only, but the description adds real behavioral context beyond them: a backup is made, manage_app closes and reopens STREONOR, force_close can discard unsaved app edits, and imported icons are normalized to 1254 x 1254 PNG. The unsaved-work warning in particular is valuable. It still omits what the expected_sha256 checks guard against or what happens on mismatch.

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?

The purpose is front-loaded and the remaining sentences each attach to a specific flag rather than restating the name. It is telegraphic and dense, but almost every clause earns its place by conveying conditional behavior.

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 24-parameter destructive mutation with zero schema description coverage and no output schema, the description is far too thin. It covers roughly a sixth of the parameters and says nothing about the meaning of the required hash guards, valid operation values, or what result is returned after applying the edit.

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% across 24 parameters, so the description carries the full burden, yet it explains only four optional booleans (manage_app, force_close, live_scene_name, live_in_place). All four required parameters (profile, operation, coordinate, expected_sha256) and specialized fields like state_index, source_coordinate, and expected_state_image_sha256 get no explanation 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?

The opening sentence gives a specific verb and resource ('Apply a previewed action/icon edit with backup'), and the word 'previewed' implicitly routes back to the preview_action_change sibling. It is clear what the tool does, though it never names the sibling outright, so the distinction relies on inference from 'previewed'.

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?

The description gives conditional guidance for four flags (manage_app, force_close, live_scene_name, live_in_place) which implies when each mode applies. However, it never states the prerequisite sequence explicitly (that preview_action_change must be run first) or when to prefer this over apply_scene_change or apply_setting_change, leaving the core routing decision to inference.

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