Skip to main content
Glama

Reconstruct

by dev.reconstruct
OverviewDiscussionsAdmin

Get scenario step image

get_scenario_step_image
Read-onlyIdempotent

Return the WebP captured after one recorded scenario step.

Input Schema

NameRequiredDescriptionDefault
stepYesOne-based scenario or replay step index from its manifest steps[].index. Must be at least 1 and identify a recorded step.
productYesProduct key, for example finance-ozon-ru
versionYesExact capture version returned by list_versions. Pin the same version across related calls; do not use latest as an alias.
scenarioYesStored scenario key returned by list_scenarios for the selected product version.
environmentNoEnvironment 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

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • 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": {
+    "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"
+}
  2. First observed

TDQS

B3.3/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 only the format (WebP) and the timing semantics (captured after the step), which is modest value but not the kind of context (auth needs, availability of the captured step, failure when no step exists) that would be most useful.

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?

A single sentence with zero filler, front-loading the action and the artifact. Nothing in it is redundant with the title and nothing is padded.

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?

The output schema exists, so return-value explanation is unnecessary, and the 100%-covered schema handles the calling contract. What is missing for a 47-sibling tool is disambiguation — the description never explains how this differs from the replay-step or initial-image variants, which is the main thing an agent must get right.

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% and every parameter carries a detailed description, including cross-references to list_versions, list_scenarios, and list_platforms. The description adds no parameter meaning of its own, so the baseline of 3 is appropriate.

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 concrete verb and resource: 'Return the WebP captured after one recorded scenario step.' The word 'after' pins the artifact to the post-step capture, which implicitly separates it from get_scenario_initial_image. However, it never names or contrasts with its closest siblings (get_replay_step_image, get_scenario_initial_image), so the differentiation is left to inference.

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 description gives no when-to-use guidance, no prerequisites, and no exclusions. With four sibling image-retrieval tools (get_replay_step_image, get_scenario_initial_image, get_capture_image, get_click_image) in the same listing, the agent gets no help choosing among them beyond the name itself.

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

All Reconstruct toolsInspect
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