Skip to main content
Glama

Get scenario step

get_scenario_step
Read-onlyIdempotent

Return one recorded scenario step with click target, pre-click state, post-click page capture, and observed CSS motion events.

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"
  }
}

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
afterNoAfter-action state
actionNoRecorded action
beforeNoBefore-action state
networkNoRequests issued after the action: method, origin, id-free path, query keys, status and body shape (keys and value types only)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed9 schema fields changed
    • removedOutput schema / $defs
      Removed value: -{
      -  "scenarioStep": {
      -    "additionalProperties": true,
      -    "description": "Stored scenario action and observed capture; fields vary with action kind",
      -    "properties": {
      -      "action": {
      -        "additionalProperties": true,
      -        "description": "Recorded action",
      -        "properties": {},
      -        "type": "object"
      -      },
      -      "after": {
      -        "additionalProperties": true,
      -        "description": "After-action state",
      -        "properties": {},
      -        "type": "object"
      -      },
      -      "before": {
      -        "additionalProperties": true,
      -        "description": "Before-action state",
      -        "properties": {},
      -        "type": "object"
      -      },
      -      "network": {
      -        "description": "Requests issued after the action: method, origin, id-free path, query keys, status and body shape (keys and value types only)",
      -        "items": {},
      -        "type": "array"
      -      }
      -    },
      -    "type": "object"
      -  }
      -}
    • changedOutput schema / additionalProperties
      Previous value: -falseNew value: +true
    • changedOutput schema / description
      Previous value: -"Structured result. Existing text or image content remains available in content."New value: +"Stored scenario action and observed capture; fields vary with action kind"
    • addedOutput schema / properties / action
      Added value: +{
      +  "additionalProperties": true,
      +  "description": "Recorded action",
      +  "properties": {},
      +  "type": "object"
      +}
    • addedOutput schema / properties / after
      Added value: +{
      +  "additionalProperties": true,
      +  "description": "After-action state",
      +  "properties": {},
      +  "type": "object"
      +}
    • addedOutput schema / properties / before
      Added value: +{
      +  "additionalProperties": true,
      +  "description": "Before-action state",
      +  "properties": {},
      +  "type": "object"
      +}
    • addedOutput schema / properties / network
      Added value: +{
      +  "description": "Requests issued after the action: method, origin, id-free path, query keys, status and body shape (keys and value types only)",
      +  "items": {},
      +  "type": "array"
      +}
    • removedOutput schema / properties / result
      Removed value: -{
      -  "$ref": "#/$defs/scenarioStep"
      -}
    • removedOutput schema / required
      Removed value: -[
      -  "result"
      -]
  2. Changed1 schema field changed
    • addedOutput schema / $defs / scenarioStep / properties / network
      Added value: +{
      +  "description": "Requests issued after the action: method, origin, id-free path, query keys, status and body shape (keys and value types only)",
      +  "items": {},
      +  "type": "array"
      +}
  3. 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": {
      +    "scenarioStep": {
      +      "additionalProperties": true,
      +      "description": "Stored scenario action and observed capture; fields vary with action kind",
      +      "properties": {
      +        "action": {
      +          "additionalProperties": true,
      +          "description": "Recorded action",
      +          "properties": {},
      +          "type": "object"
      +        },
      +        "after": {
      +          "additionalProperties": true,
      +          "description": "After-action state",
      +          "properties": {},
      +          "type": "object"
      +        },
      +        "before": {
      +          "additionalProperties": true,
      +          "description": "Before-action state",
      +          "properties": {},
      +          "type": "object"
      +        }
      +      },
      +      "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/scenarioStep"
      +    }
      +  },
      +  "required": [
      +    "result"
      +  ],
      +  "type": "object"
      +}
  4. First observed

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, and destructiveHint=false, so the safety profile is covered. The description adds a characterization of the returned step contents, which is useful framing but largely duplicates what the output schema supplies, and it says nothing about failures, missing steps, or environment availability 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?

A single front-loaded sentence with zero filler, naming the resource first and then its contents. Nothing is wasted.

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?

With annotations, a full output schema, and 100% parameter coverage, the definition is adequate for calling the tool. What is missing is disambiguation from the dense set of replay/scenario/image siblings, which is the main decision an agent faces here.

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 one-based step index, pinned version, scenario key, and environment) are already well documented in the schema. The description adds no additional meaning about parameter interaction or selection, 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 and resource ("Return one recorded scenario step") and enumerates the payload's contents: click target, pre-click state, post-click page capture, and CSS motion events. It never distinguishes this from close siblings such as get_replay_step, get_scenario_step_image, or get_scenario_manifest, so an agent must infer the boundary itself.

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?

The required inputs are described in the schema, but the description gives no explicit when-to-use guidance, no prerequisites, and no alternatives. With 60+ siblings including get_replay_step and get_scenario_step_image, the absence of any routing hint is a real gap; usage is only implied by the name.

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