Reconstruct

Get capture image

get_capture_image

Read-onlyIdempotent

Read one allowlisted WebP from a product version by relative path (for example before.webp, capture/pages/home/desktop/viewport.webp). Only .webp paths present in storage are readable.

Input Schema

Name	Required	Description
`path`	Yes	Capture-relative archived file path returned by an inventory tool. Use forward slashes; absolute paths and traversal are not allowed.
`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.
`platform`	Yes	Platform type ID from list_platforms.options.platforms[].id (backend CatalogPlatform.view). Use backend IDs verbatim; desktop/mobile are current examples. Environment is selected separately.
`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.

Changed3 schema fields changedOct 12, 2026

addedInput schema / properties / path / description

Added value: +"Capture-relative archived file path returned by an inventory tool. Use forward slashes; absolute paths and traversal are not allowed."

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.9/5.0

Behavior4/5

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

Annotations already declare readOnlyHint/idempotentHint/non-destructive, so the safety profile is covered. The description adds real behavioral context beyond that: only allowlisted WebP files are readable, paths must be relative and present in storage. It stops short of describing what happens on a missing or non-allowlisted path (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?

Two tight sentences, front-loaded with the core action and scope, followed by the readability constraint. No filler, no repetition of the title or schema fields.

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

Completeness5/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 details need not be explained. Combined with 100% parameter coverage and annotated safety hints, the description supplies everything required to invoke correctly: what is read, in what format, and the allowlisting constraint.

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 already documents all five parameters with detail (path format, product key, pinned version, platform/environment IDs). The description adds only concrete example paths, which is marginal value over the schema, so the 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 ('Read one allowlisted WebP from a product version by relative path') and even supplies example paths, so the agent knows exactly what it retrieves. However, it does not differentiate this tool from the many sibling image retrievers (get_capture_asset, get_page_image, get_stage_image, get_component_image), leaving the agent to infer which image source applies.

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 implied rather than stated: the agent should call this when it holds a relative .webp path from an inventory tool. The phrase 'Only .webp paths present in storage are readable' establishes a boundary condition, but there is no explicit when-to-use/when-not guidance or named alternative among the image siblings.

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?