Skip to main content
Glama
STREONOR MCP

STREONOR MCP

by lde-medeiros

preview_action_change

Read-only

Preview controller action, icon, hotkey, and flow changes in a STREONOR profile before applying them to slots.

Instructions

Preview action/icon edits. create_by_name fills an empty slot from installed action_name or UUID. replace_by_name swaps an occupied slot in one write and keeps existing state icons by default. Supply image_path, state_images, or an automatic icon_query to select a replacement. Supply hotkey, for example Ctrl+Shift+P, with create_by_name or replace_by_name and the installed Hotkey or HotkeySwitch action. HotkeySwitch sends the same chord in both states. configure_action replaces settings for an existing slot. Plugin-specific execution is not verified by creation alone. Other operations: set_flow replaces a key with ordered steps cloned from same-page source_coordinate actions, optional settings overrides and delay_ms. Supply flow_steps and flow_title. New actions and flows get matching icons by default. auto_icon=False opts out and icon_query supplies a name. For icon operations state_index selects the image state, starting at 0. Use set_state_icons or supply state_images with create_by_name or replace_by_name to apply preferred images by state index together. PNG, JPEG, BMP, GIF, and WebP imports become 1254 x 1254 PNG with transparent padding.

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

Input Schema

NameRequiredDescriptionDefault
pageNo
hotkeyNo
profileYes
auto_iconNo
operationYes
controllerNoKeypad
coordinateYes
flow_stepsNo
flow_titleNo
icon_queryNo
image_pathNo
action_nameNo
state_indexNo
state_imagesNo
action_settingsNo
source_coordinateNo

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?

Beyond the readOnly and non-destructive annotations, it discloses useful behavior: replace_by_name keeps existing state icons by default, HotkeySwitch sends the same chord in both states, auto_icon=False opts out of default icons, and imported images become 1254x1254 PNGs. It still does not explain what a preview returns or whether the preview is exactly what apply_action_change would commit.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single dense paragraph covering many operations, parameters, and edge cases without bullets or clear grouping. The content is relevant, but the run-on structure makes it hard to scan and front-loads operation-name details before broader usage guidance.

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 16-parameter tool with no output schema and no schema descriptions, the definition is incomplete: it never explains the preview return value, omits several required parameter meanings, and does not fully enumerate operation values. It provides substantial behavioral detail but not enough to call this tool correctly without consulting the schema and annotations.

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%, so the description must carry parameter meaning, and it does explain action_name, image_path, state_images, icon_query, hotkey, flow_steps, flow_title, auto_icon, state_index, and source_coordinate. It leaves required parameters such as profile and coordinate unexplained, and several other parameters, including page, controller, and action_settings, get little or no semantic detail.

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, "Preview action/icon edits," gives a clear verb and resource, and later clauses clarify that it also covers flows. It does not distinguish this preview tool from apply_action_change or explain the preview/apply relationship, so sibling differentiation is missing.

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 operation-level guidance such as create_by_name for an empty slot, replace_by_name for an occupied slot, and configure_action for existing settings. However, it never states when to use this tool versus apply_action_change, nor when not to use it.

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