Reconstruct

Get scenario initial image

get_scenario_initial_image

Read-onlyIdempotent

Return the initial WebP from a recorded scenario for an exact stored view key in the selected environment.

Input Schema

Name	Required	Description
`view`	Yes	Exact stored profile key from list_pages.views (desktop, mobile, numbered profiles or a device label); do not pass the operating system here.
`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.

Changed4 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 / 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

A3.5/5.0

Behavior3/5

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

Annotations already declare readOnlyHint/idempotentHint true and destructiveHint false, so the safety profile is covered. The description adds one genuinely useful behavioral fact – the return format is WebP – but says nothing about size, caching, failure modes, or permissions. Appropriate credit for the format disclosure, no more.

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; the resource and both scoping constraints are packed in efficiently. It is tight, though terse enough that it omits any routing guidance that could have earned space.

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?

With an output schema present, return values need not be explained, and annotations carry the safety profile; the schema itself fully documents all five parameters. The description is sufficient for an agent to call this correctly, missing only explicit sibling routing.

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 parameters such as view, product, version, scenario, and environment are already richly documented in the schema, including how to obtain each key. The description only echoes the 'exact stored view key' and 'selected environment' constraints, adding no format or syntax detail beyond the schema. 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?

The description gives a specific verb and resource ('Return the initial WebP from a recorded scenario') plus scoping qualifiers ('exact stored view key in the selected environment'), which distinguishes it from step/capture/page image siblings by the word 'initial'. It does not explicitly name a sibling to contrast with, 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 Guidelines3/5

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

Usage is only implied: 'initial' versus a step image implies this is the first-frame variant, and the schema descriptions reference list_pages/list_versions/list_scenarios for obtaining keys, hinting at the workflow. There is no explicit when-to-use/when-not statement or named alternative (e.g., get_scenario_step_image).

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?