Skip to main content
Glama
STREONOR MCP

STREONOR MCP

by lde-medeiros

preview_scene_creation

Read-only

Preview a new scene for a source device before saving, optionally copying button, knob, flow, and PNG icon coordinates while checking catalog and duplicate names.

Instructions

Preview a new scene for the source device. Optionally copy include_coordinates from the source (buttons, knobs, flows and PNG icons). Checks catalog and duplicate names.

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": {
      "source_profile": "<source_profile>",
      "name": "<name>"
    },
    "name": "preview_scene_creation"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
source_profileYes
include_coordinatesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.8.2

TDQS

B3.2/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description does add genuine non-annotation behavior: it validates against the catalog and detects duplicate names, which tells the agent the call can fail on naming conflicts. It does not say what the preview returns or how validation failures surface, leaving a gap for a tool with no output schema.

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 with the action front-loaded and no filler. Minor deduction for the awkward middle sentence, which conflates the parameter name with the concept being copied.

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 three-parameter tool with no output schema, the definition says what it does and that it validates names, but omits what the preview actually contains and what the caller should do with the result. Combined with 0% parameter coverage, an agent knows the intent but must guess at argument formats and return shape.

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 never explains 'name' or 'source_profile' (what a source profile identifier looks like, or what naming rules the duplicate check enforces). The one sentence about include_coordinates is awkwardly phrased ('copy include_coordinates from the source') and does add meaning by naming the element types (buttons, knobs, flows, PNG icons), but it reads as a description of behavior rather than of the parameter.

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?

States a specific verb and resource ('Preview a new scene for the source device'), which clearly separates it from apply_scene_change and create_scene by implication. It stops short of naming a sibling or stating the boundary explicitly, so an agent must infer that this is the non-committing counterpart.

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' plus the presence of apply_scene_change sibling tools implies this is the dry-run step before creating a scene, but no sentence says when to use it, when not to, or that it must precede a create/apply call. Usage is implied rather than stated.

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