Skip to main content
Glama

Get replay step

get_replay_step
Read-onlyIdempotent

Return one replay step result.json (pass/fail and observed outcome).

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>",
      "replay": "<replay>",
      "step": "<step>"
    },
    "name": "get_replay_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.
replayYesStored replay key returned by list_replays for the selected product version.
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.
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
errorNo
passedNoWhether this condition holds

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changed
    • removedOutput schema / $defs
      Removed value: -{
      -  "replayStep": {
      -    "additionalProperties": true,
      -    "description": "Stored replay result with observed outcome; only recorded evidence is returned",
      -    "properties": {
      -      "error": {
      -        "anyOf": [
      -          {
      -            "description": "Text value",
      -            "type": "string"
      -          },
      -          {
      -            "type": "null"
      -          }
      -        ]
      -      },
      -      "passed": {
      -        "description": "Whether this condition holds",
      -        "type": "boolean"
      -      }
      -    },
      -    "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 replay result with observed outcome; only recorded evidence is returned"
    • addedOutput schema / properties / error
      Added value: +{
      +  "anyOf": [
      +    {
      +      "description": "Text value",
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ]
      +}
    • addedOutput schema / properties / passed
      Added value: +{
      +  "description": "Whether this condition holds",
      +  "type": "boolean"
      +}
    • removedOutput schema / properties / result
      Removed value: -{
      -  "$ref": "#/$defs/replayStep"
      -}
    • removedOutput schema / required
      Removed value: -[
      -  "result"
      -]
  2. Changed5 schema fields changed
    • addedInput schema / properties / product / description
      Added value: +"Product key, for example finance-ozon-ru"
    • addedInput schema / properties / replay / description
      Added value: +"Stored replay key returned by list_replays 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": {
      +    "replayStep": {
      +      "additionalProperties": true,
      +      "description": "Stored replay result with observed outcome; only recorded evidence is returned",
      +      "properties": {
      +        "error": {
      +          "anyOf": [
      +            {
      +              "description": "Text value",
      +              "type": "string"
      +            },
      +            {
      +              "type": "null"
      +            }
      +          ]
      +        },
      +        "passed": {
      +          "description": "Whether this condition holds",
      +          "type": "boolean"
      +        }
      +      },
      +      "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/replayStep"
      +    }
      +  },
      +  "required": [
      +    "result"
      +  ],
      +  "type": "object"
      +}
  3. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already establish that this is read-only, idempotent, and non-destructive, so the description does not need to restate safety. It adds useful behavioral context by saying the response contains pass/fail and observed outcome, but it does not mention failure modes, missing-step behavior, or any access constraints. With annotations covering the safety profile, a 3 is appropriate.

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?

The description is a single front-loaded sentence with no filler or repetition. It states the operation and returned content directly, so every word earns its place.

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?

The rich input schema and the presence of an output schema mean the description does not need to explain return structure or parameter usage in detail. For a simple getter, it is largely complete, though it would benefit from sibling differentiation to avoid confusion with adjacent replay and scenario tools.

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 input schema already documents all five parameters, including the one-based step index and replay key. The description adds no parameter-level meaning beyond what the schema provides, which fits the baseline 3 when schema coverage is high.

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 uses a specific verb and resource ('Return one replay step result.json') and states the returned content (pass/fail and observed outcome). It is clear what the tool does, but it does not differentiate itself from close siblings such as get_replay_manifest, get_replay_step_image, or get_scenario_step.

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?

There is no explicit when-to-use guidance, no exclusion criteria, and no alternative tool named. The schema implies that callers need a product, version, replay, and step, but the description itself does not help an agent choose this tool over related retrieval tools.

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