Skip to main content
Glama
STREONOR MCP

STREONOR MCP

by lde-medeiros

apply_setting_change

Destructive

Apply a previewed STREONOR setting edit with backup, optionally restarting or force-closing the app, and import the edit into a live scene on Windows.

Instructions

Apply a previewed setting 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. A changed hash requires a new preview.

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>",
      "coordinate": "<coordinate>",
      "setting": "<setting>",
      "new_value": "<new_value>",
      "expected_sha256": "<expected_sha256>"
    },
    "name": "apply_setting_change"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNo
profileYes
settingYes
auto_iconNo
new_valueYes
coordinateYes
icon_queryNo
manage_appNo
force_closeNo
expected_sha256Yes
live_scene_nameNo
expected_auto_icon_sha256No

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.8.2

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the description is not carrying the full safety burden, yet it adds real value: a backup is taken, manage_app closes and reopens STREONOR, force_close discards unsaved edits, and live_scene_name imports into a new scene while the app runs. It does not say where the backup lives, whether it is reversible, or what the hash-mismatch failure looks like.

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?

Four tight sentences, with the primary action and its backup behavior front-loaded and the risky flags addressed immediately after. Every sentence carries operational information; no filler or restatement of the title.

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 destructive, 12-parameter mutation with no output schema, the description covers the dangerous options well but leaves the identity parameters (how coordinate, page, and profile are obtained and what form they take) unaddressed. An agent would still need to infer the coordinate format and the icon-related fields from the schema alone.

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 compensate for all 12 parameters, and it explains only four of them (manage_app, force_close, live_scene_name, expected_sha256). Names like profile, setting, new_value, and coordinate are largely self-describing, but auto_icon, icon_query, and expected_auto_icon_sha256 receive no explanation anywhere.

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 opens with a specific verb and resource ('Apply a previewed setting edit with backup') and makes the preview prerequisite explicit, which implicitly separates it from preview_setting_change. It stops short of naming the sibling tool or stating the full scope of what 'setting edit' covers, but an agent can still tell what this does.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It states the precondition clearly ('A changed hash requires a new preview') and gives conditional guidance for the two risky flags, including that force_close can discard unsaved app edits and that live_scene_name is Windows-only. What is missing is any explicit statement of when NOT to use this tool versus apply_action_change or apply_scene_change.

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