Skip to main content
Glama
STREONOR MCP

STREONOR MCP

by lde-medeiros

preview_page_order

Read-only

Preview a new order for all existing pages using page IDs from the scene registry before applying changes.

Instructions

Preview a new order for all existing pages. Use the page IDs from the scene registry.

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

Input Schema

NameRequiredDescriptionDefault
profileYes
page_orderYes

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, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds that it validates against all existing pages and that IDs must come from the scene registry, but it never says what the preview actually reports (errors for bad IDs? final arrangement?) — relevant since there is 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?

Two short sentences, front-loaded with the action and followed by the input-source hint; no filler. It is terse to the point of leaving gaps, but the wording itself earns its place.

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 preview/validation tool with no output schema and 0% parameter coverage, the agent needs to know what the preview returns and what 'profile' means. Neither is addressed, so the definition is under-specified relative to the tool's role.

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 must carry the burden. It explains that page_order holds page IDs sourced from the scene registry, which is useful, but the required 'profile' parameter is never mentioned or explained.

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+resource: 'Preview a new order for all existing pages.' The scope ('all existing pages') is clear, and the preview-vs-apply distinction against siblings like reorder_pages is inferable from the verb, though no sibling is named explicitly.

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?

Usage is only implied — the word 'Preview' suggests checking before an apply step, and 'Use the page IDs from the scene registry' hints at where inputs come from, but the description never says when to use this instead of reorder_pages or what condition makes preview necessary.

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