Skip to main content
Glama
STREONOR MCP

STREONOR MCP

by lde-medeiros

apply_scene_change

Destructive

Rename or delete a previewed STREONOR scene with backup safeguards; deletion unregisters the scene and archives its folder, with optional app close/reopen control.

Instructions

Rename/delete a previewed scene with backups. Deletion unregisters it and archives its entire folder. Optionally close/reopen Windows STREONOR.

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>",
      "expected_sha256": "<expected_sha256>",
      "expected_registry_sha256": "<expected_registry_sha256>"
    },
    "name": "apply_scene_change"
  }
}

Input Schema

NameRequiredDescriptionDefault
profileYes
new_nameNo
operationYes
manage_appNo
force_closeNo
expected_sha256Yes
expected_registry_sha256Yes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.8.2

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the safety profile is known; the description nevertheless adds real value by disclosing that backups are made, that deletion unregisters the scene and archives its whole folder, and that STREONOR may be closed and reopened. It omits the semantics of the two expected_*_sha256 guard parameters, which are the main behavioral risk for a destructive call.

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?

Three short sentences, front-loaded with the core action and consequences. Slightly terse for the number of undocumented parameters, but no sentence is wasted.

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 destructive 7-parameter mutation with no output schema and zero schema descriptions, explaining how to obtain the expected hashes and what each flag does is essential and absent. The description covers consequences but not the mechanics required to call it successfully.

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%, so the description must carry the parameter burden and largely fails. Only a vague hint at manage_app/force_close ('optionally close/reopen Windows STREONOR') is offered, and expected_sha256, expected_registry_sha256, new_name and the allowed values of operation remain completely unexplained — an agent cannot tell these are optimistic-concurrency tokens or which operations are valid.

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 names specific verbs (rename/delete) and a specific resource (a previewed scene), and the apply-vs-preview contrast with preview_scene_change is inferable from the verb. It does not explicitly name the sibling it pairs with, but an agent can distinguish apply from preview without opening a schema.

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?

'previewed scene' implies this is the commit step after preview_scene_change, but the description never states that precondition or any when-not condition. There is no mention of whether the scene must exist, or what to do if the preview is stale.

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