Skip to main content
Glama
STREONOR MCP

STREONOR MCP

by lde-medeiros

preview_scene_layout

Read-only

Preview a named copy of a scene layout with edits across existing pages, including controls, Action Flows, icons, and replace options before applying changes.

Instructions

Preview a named copy with changes across existing pages. Each page uses its ID or an empty ID for the main page. Controls are keyed by coordinate. Supply action_name to create or replace a control, flow_steps and flow_title to place an Action Flow, settings or an icon to edit an existing control, or null to remove it. Use state_index to pick an icon state. Set replace=True to clear unlisted controls on a page.

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

Input Schema

NameRequiredDescriptionDefault
nameYes
pagesYes
profileYes

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?

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description still adds real behavioral detail beyond them: page addressing via ID or empty string for the main page, controls keyed by coordinate, and the replace=True semantics that clear unlisted controls. It does not clarify what the preview actually returns or how the named copy is identified.

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?

Six short sentences, front-loaded with the purpose and then ordered from page-level to control-level to flag-level concerns. The density of jargon ('Action Flow', 'keyed by coordinate') is high, but nearly every clause carries distinct information and nothing is repeated.

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 tool whose name promises a preview and which has no output schema, the description should say what a preview yields (an image, a layout object, a diff), and it does not. Combined with the undocumented 'profile' and 'name' required parameters, the definition is workable but leaves an agent guessing at both inputs and results.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/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 full load, and it does explain the important ControlEdit interactions — action_name to create or replace, flow_steps/flow_title for an Action Flow, settings or icon to edit, null to remove, state_index for icon state, replace for wholesale page control clearing. Critical gaps remain: the required 'profile' parameter and the 'name' of the copy are never explained, so two of three top-level required arguments are undefined.

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 opening sentence states a concrete verb and resource — previewing a named copy with page-level changes — so an agent knows this produces a dry-run layout rather than a mutation. It does not, however, distinguish itself from siblings such as preview_scene_change or preview_scene_creation, nor does it point at apply_scene_layout as the 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 Guidelines2/5

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

The word 'Preview' implies a non-committal dry run, but the description never says when to choose this over apply_scene_layout or the other preview_* siblings, and never states that nothing is persisted. There are no exclusions or alternatives named, leaving the agent to infer routing from the name alone.

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