Skip to main content
Glama
STREONOR MCP

STREONOR MCP

by lde-medeiros

create_scene

Destructive

Create and register a previewed scene in STREONOR, back up its catalog, and optionally copy selected coordinates and PNG icons or close/reopen the Windows app.

Instructions

Create a previewed scene and register it in STREONOR, backing up its catalog. Optional include_coordinates copies selected source actions and PNG icons. Optionally close/reopen the Windows app.

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>",
      "expected_source_sha256": "<expected_source_sha256>",
      "expected_registry_sha256": "<expected_registry_sha256>"
    },
    "name": "create_scene"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
manage_appNo
force_closeNo
source_profileYes
include_coordinatesNo
expected_source_sha256Yes
expected_registry_sha256Yes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.8.2

TDQS

C2.6/5.0
Behavior3/5

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

Annotations already flag destructiveHint=true and openWorldHint=false, so the safety profile is covered. The description adds real context beyond them: it registers into STREONOR, backs up the catalog, and can close/reopen the Windows app. However, it never says what the destructive action overwrites or whether the app restart is required, leaving the destructiveHint unexplained.

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

Conciseness3/5

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

Three sentences, front-loaded with the core action, with no filler. But cryptic domain terms (STREONOR, 'previewed scene') go unexplained, and the optional-behavior clauses read as a parameter dump rather than coherent 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?

A destructive 7-parameter mutation with 4 required fields, zero schema descriptions, and no output schema needs more than this. The required checksum parameters and the source_profile semantics are undocumented anywhere, and there is no indication of what the call returns or how failures surface.

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% across 7 parameters, so the description carries the full burden. It only gestures at include_coordinates ('copies selected source actions and PNG icons') and manage_app/force_close ('close/reopen the Windows app'), leaving name, source_profile, and especially the two required expected_*_sha256 concurrency tokens completely opaque.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The verb+resource pair (create a scene) is stated, and side effects like registering in STREONOR and backing up the catalog are named. But 'Create a previewed scene' blurs whether this only previews or actually commits, which matters because a sibling is literally named preview_scene_creation. The description never distinguishes itself from that sibling.

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

Usage Guidelines2/5

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

There is no when-to-use or when-not-to-use guidance, no prerequisite or ordering information, and no reference to alternatives such as preview_scene_creation, preview_scene_change, or apply_scene_change. An agent must infer from the tool name alone whether this is the preview or the commit step.

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