Reconstruct

Get replay step image

get_replay_step_image

Read-onlyIdempotent

Return the after.webp captured for one replay step, when present.

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.
`replay`	Yes	Stored replay key returned by list_replays for the selected product version.
`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.
`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.

Changed5 schema fields changedOct 12, 2026

addedInput schema / properties / product / description

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

addedInput schema / properties / replay / description

Added value: +"Stored replay key returned by list_replays 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": {
+    "image": {
+      "additionalProperties": false,
+      "description": "Metadata for the image in content[contentIndex]; image bytes are not duplicated here",
+      "properties": {
+        "contentIndex": {
+          "const": 0,
+          "description": "Zero-based index of the ImageContentBlock",
+          "type": "integer"
+        },
+        "mimeType": {
+          "description": "MIME type of the returned image",
+          "type": "string"
+        }
+      },
+      "required": [
+        "mimeType",
+        "contentIndex"
+      ],
+      "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/image"
+    }
+  },
+  "required": [
+    "result"
+  ],
+  "type": "object"
+}

First observedOct 12, 2026

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, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds one useful behavioral note with 'when present,' signalling an optional/absent result, but says nothing about how absence is surfaced or how the webp is returned. Additive but thin.

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?

A single front-loaded sentence with no filler, identifying the resource before the availability caveat. It is appropriately sized for a simple fetcher, though it is arguably too terse to carry much operational value.

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?

An output schema exists, so return-value explanation is unnecessary, and 'when present' covers the absent-artifact case. However, given the four-required-parameter key chain (product/version/replay/step) shared with list_replays and get_replay_step, the description does not tie itself to that workflow, leaving the agent to reconstruct it from the schema alone.

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 all five parameters (including the replay/version/step key chain and the environment default) are already documented in the schema. The description adds no format or relationship detail beyond what the schema provides, so baseline 3 applies.

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 (Return) and a precise resource (the after.webp captured for one replay step), which distinguishes it from image siblings like get_scenario_step_image or get_page_image. It does not explicitly name those alternatives, so it falls short of a 5.

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 only guidance is the trailing 'when present,' which hints the artifact may be absent but gives no when-to-use condition, no prerequisites, and no routing versus the other image-fetching siblings. Usage is left to inference.

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?