Reconstruct

Get scenario step

get_scenario_step

Read-onlyIdempotent

Return one recorded scenario step with click target, pre-click state, post-click page capture, and observed CSS motion events.

Input Schema

Name	Required	Description
`step`	Yes	One-based scenario or replay step index from its manifest steps[].index. Must be at least 1 and identify a recorded step.
`product`	Yes	Product key, for example finance-ozon-ru
`version`	Yes	Exact capture version returned by list_versions. Pin the same version across related calls; do not use latest as an alias.
`scenario`	Yes	Stored scenario key returned by list_scenarios for the selected product version.
`environment`	No	Environment ID from the selected backend platform type in list_platforms.options.platforms[].environments[].id (backend implementation). Omit only when the version has one captured environment. Use captured pairs from list_platforms/list_versions for actual availability.

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 16, 2026

addedOutput schema / $defs / scenarioStep / properties / network

Added value: +{
+  "description": "Requests issued after the action: method, origin, id-free path, query keys, status and body shape (keys and value types only)",
+  "items": {},
+  "type": "array"
+}

Changed5 schema fields changedOct 12, 2026

addedInput schema / properties / product / description

Added value: +"Product key, for example finance-ozon-ru"

addedInput schema / properties / scenario / description

Added value: +"Stored scenario key returned by list_scenarios for the selected product version."

addedInput schema / properties / step / description

Added value: +"One-based scenario or replay step index from its manifest steps[].index. Must be at least 1 and identify a recorded step."

addedInput schema / properties / version / description

Added value: +"Exact capture version returned by list_versions. Pin the same version across related calls; do not use latest as an alias."

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$defs": {
+    "scenarioStep": {
+      "additionalProperties": true,
+      "description": "Stored scenario action and observed capture; fields vary with action kind",
+      "properties": {
+        "action": {
+          "additionalProperties": true,
+          "description": "Recorded action",
+          "properties": {},
+          "type": "object"
+        },
+        "after": {
+          "additionalProperties": true,
+          "description": "After-action state",
+          "properties": {},
+          "type": "object"
+        },
+        "before": {
+          "additionalProperties": true,
+          "description": "Before-action state",
+          "properties": {},
+          "type": "object"
+        }
+      },
+      "type": "object"
+    }
+  },
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "additionalProperties": false,
+  "description": "Structured result. Existing text or image content remains available in content.",
+  "properties": {
+    "result": {
+      "$ref": "#/$defs/scenarioStep"
+    }
+  },
+  "required": [
+    "result"
+  ],
+  "type": "object"
+}

First observedOct 12, 2026

TDQS

A3.6/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering the safety profile. The description adds a summary of the returned payload, but since an output schema exists this overlaps structured metadata and discloses no auth requirements, rate limits, or error behavior.

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?

Single sentence, front-loaded with the verb and resource, with no filler. Every element of the sentence contributes to identifying the tool's output.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple read-only getter with complete parameter descriptions and an existing output schema, the description adequately identifies the resource and its payload. The only notable gap is the lack of usage routing against sibling step tools.

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 100%, so the schema fully documents all five parameters. The description adds no parameter-level syntax or format details beyond what the schema already provides, making the baseline 3 appropriate.

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

Purpose5/5

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

States a specific verb 'Return' and resource 'one recorded scenario step', then enumerates the payload (click target, pre-click state, post-click page capture, and observed CSS motion events). This distinguishes it from siblings like get_scenario_step_image or get_replay_step.

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?

Provides no explicit when-to-use or when-not-to-use guidance. It does not contrast with alternatives such as get_replay_step or get_scenario_step_image, so an agent must infer selection from the resource name alone.

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

All Reconstruct tools Inspect

Try in Browser

Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?