Skip to main content
Glama
STREONOR MCP

STREONOR MCP

by lde-medeiros

apply_scene_layout

Apply a previewed scene layout to the running STREONOR app as a new scene using its layout_sha256, while keeping the source scene available.

Instructions

Apply the exact previewed layout as a new scene in the running Windows STREONOR app. Use the layout_sha256 from preview_scene_layout. The source scene remains available.

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>",
      "name": "<name>",
      "pages": "<pages>",
      "expected_layout_sha256": "<expected_layout_sha256>"
    },
    "name": "apply_scene_layout"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
pagesYes
profileYes
expected_layout_sha256Yes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.8.2

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare non-destructive, non-read-only, non-idempotent behavior, and the description adds real context: the target must be the running STREONOR app, the result is a new scene, and "the source scene remains available." It does not say what happens when the expected checksum mismatches (presumably a hard failure), which is the one behavioral gap left.

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

Conciseness5/5

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

Three short sentences, front-loaded with the action and outcome, followed by the prerequisite and the safety note. No filler and nothing repeated from annotations or schema.

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 mutation tool with a deeply nested pages schema, no output schema, and zero schema descriptions, the definition covers workflow and safety well but says nothing about the structure or semantics of profile/name/pages. An agent can sequence the call but needs the schema alone to build the payload.

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% and three of four parameters (profile, name, pages with its nested PageEdit/ControlEdit structures) are never mentioned in the description. Only the checksum parameter is explained, and even then the description says "layout_sha256" while the schema field is "expected_layout_sha256", leaving the agent to infer the mapping.

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?

"Apply the exact previewed layout as a new scene" gives a specific verb, resource, and outcome, and the phrase "previewed layout" implicitly separates it from create_scene and apply_scene_change. It does not call out those siblings by name, so differentiation is inferential rather than explicit.

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?

"Use the layout_sha256 from preview_scene_layout" establishes a clear prerequisite chain, telling the agent to run the preview tool first and pass its token. There is no explicit statement of when not to use it or when to prefer apply_scene_change/create_scene instead.

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