Skip to main content
Glama

Get scenario step image

get_scenario_step_image
Read-onlyIdempotent

Return the WebP captured after one recorded scenario step.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "product": "<product>",
      "version": "<version>",
      "scenario": "<scenario>",
      "step": "<step>"
    },
    "name": "get_scenario_step_image"
  }
}

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
mimeTypeYesMIME type of the returned image
contentIndexYesZero-based index of the ImageContentBlock

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changed
    • removedOutput schema / $defs
      Removed value: -{
      -  "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"
      -  }
      -}
    • changedOutput schema / description
      Previous value: -"Structured result. Existing text or image content remains available in content."New value: +"Metadata for the image in content[contentIndex]; image bytes are not duplicated here"
    • addedOutput schema / properties / contentIndex
      Added value: +{
      +  "const": 0,
      +  "description": "Zero-based index of the ImageContentBlock",
      +  "type": "integer"
      +}
    • addedOutput schema / properties / mimeType
      Added value: +{
      +  "description": "MIME type of the returned image",
      +  "type": "string"
      +}
    • removedOutput schema / properties / result
      Removed value: -{
      -  "$ref": "#/$defs/image"
      -}
    • changedOutput schema / required
      Previous value: -[
      -  "result"
      -]New value: +[
      +  "mimeType",
      +  "contentIndex"
      +]
  2. 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"
      +}
  3. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is fully covered by structured data. The description adds only the output format (WebP) and timing (post-step); it says nothing about behavior when the step is missing, version mismatch, or whether the image is captured before or after the step action completes.

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 front-loaded sentence with no filler and no repetition of the title. Every word contributes to identifying the resource and its timing.

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, the description need not explain return values, and full schema coverage handles parameters and annotations handle safety. The remaining gap is behavioral edge cases (missing step, unavailable capture), which is minor for a read-only retrieval tool.

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 the schema already explains step indexing (one-based, from manifest steps[].index), version pinning, and environment derivation. The description contributes no additional parameter meaning beyond what the schema states, 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 names a specific verb ("Return") and resource ("the WebP captured after one recorded scenario step"), which separates it from get_scenario_initial_image and get_replay_step_image by the 'after a step' qualifier. It never names the siblings explicitly, so an agent still has to infer the distinction.

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 by "after one recorded scenario step"; the agent can infer this is the post-step screenshot rather than the initial image, but there is no explicit when-to-use/when-not statement or named alternative such as get_replay_step_image or get_scenario_initial_image.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources