Skip to main content
Glama
STREONOR MCP

STREONOR MCP

by lde-medeiros

preview_scene_change

Read-only

Preview renaming or deleting a registered scene before applying changes; blocks deletion of the last scene.

Instructions

Preview renaming or deleting a registered scene. Last-scene deletion is refused.

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

Input Schema

NameRequiredDescriptionDefault
profileYes
new_nameNo
operationYes

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 readOnlyHint=true and destructiveHint=false, which matches the preview framing. The description adds one genuinely non-obvious behavioral rule (the last scene cannot be deleted, even in preview), but says nothing about what the preview returns, whether it mutates anything, or how invalid operations fail.

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?

Two short, front-loaded sentences with no filler and the refusal rule placed immediately after the purpose. Nothing is wasted, though the extreme brevity leaves the parameter gaps untouched.

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 3-parameter tool with zero schema documentation and no output schema, the description should explain valid operation values, the role of profile, and what a preview returns. Neither is covered, so an agent could not construct a confident call from the definition alone.

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 carries the full burden, yet it only hints that "operation" takes rename/delete and that a name matters for renaming. The required "profile" parameter and new_name's empty default are completely undocumented 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?

"Preview renaming or deleting a registered scene" gives a specific verb (preview) and resource (scene), and the rename/delete distinction separates it from layout/setting/action preview siblings. It never names the corresponding apply_scene_change tool, so the differentiation is implied rather than stated.

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 word "preview" implies look-before-you-apply, and "Last-scene deletion is refused" flags one refusal case, but the description never says to call apply_scene_change afterward or when to skip preview entirely. Usage is inferable but not spelled out.

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