Skip to main content
Glama

Get scenario manifest

get_scenario_manifest
Read-onlyIdempotent

Return the manifest of one recorded scenario, including step order, view, action, and route transitions.

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>"
    },
    "name": "get_scenario_manifest"
  }
}

Input Schema

NameRequiredDescriptionDefault
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
stepsNoResult entries
sourceNo
startedAtNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed8 schema fields changed
    • removedOutput schema / $defs
      Removed value: -{
      -  "scenarioManifest": {
      -    "additionalProperties": true,
      -    "description": "Stored scenario manifest; optional fields follow the recorder format",
      -    "properties": {
      -      "source": {
      -        "anyOf": [
      -          {
      -            "description": "source",
      -            "type": "string"
      -          },
      -          {
      -            "type": "null"
      -          }
      -        ]
      -      },
      -      "startedAt": {
      -        "anyOf": [
      -          {
      -            "description": "startedAt",
      -            "type": "string"
      -          },
      -          {
      -            "type": "null"
      -          }
      -        ]
      -      },
      -      "steps": {
      -        "description": "Result entries",
      -        "items": {
      -          "additionalProperties": true,
      -          "description": "Recorded scenario step metadata",
      -          "properties": {},
      -          "type": "object"
      -        },
      -        "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 manifest; optional fields follow the recorder format"
    • removedOutput schema / properties / result
      Removed value: -{
      -  "$ref": "#/$defs/scenarioManifest"
      -}
    • addedOutput schema / properties / source
      Added value: +{
      +  "anyOf": [
      +    {
      +      "description": "source",
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ]
      +}
    • addedOutput schema / properties / startedAt
      Added value: +{
      +  "anyOf": [
      +    {
      +      "description": "startedAt",
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ]
      +}
    • addedOutput schema / properties / steps
      Added value: +{
      +  "description": "Result entries",
      +  "items": {
      +    "additionalProperties": true,
      +    "description": "Recorded scenario step metadata",
      +    "properties": {},
      +    "type": "object"
      +  },
      +  "type": "array"
      +}
    • removedOutput schema / required
      Removed value: -[
      -  "result"
      -]
  2. Changed4 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 / 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": {
      +    "scenarioManifest": {
      +      "additionalProperties": true,
      +      "description": "Stored scenario manifest; optional fields follow the recorder format",
      +      "properties": {
      +        "source": {
      +          "anyOf": [
      +            {
      +              "description": "source",
      +              "type": "string"
      +            },
      +            {
      +              "type": "null"
      +            }
      +          ]
      +        },
      +        "startedAt": {
      +          "anyOf": [
      +            {
      +              "description": "startedAt",
      +              "type": "string"
      +            },
      +            {
      +              "type": "null"
      +            }
      +          ]
      +        },
      +        "steps": {
      +          "description": "Result entries",
      +          "items": {
      +            "additionalProperties": true,
      +            "description": "Recorded scenario step metadata",
      +            "properties": {},
      +            "type": "object"
      +          },
      +          "type": "array"
      +        }
      +      },
      +      "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/scenarioManifest"
      +    }
      +  },
      +  "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=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered without description help. The description adds value by enumerating what the manifest contains, but says nothing about version pinning behavior, environment selection, or result size/pagination that would go beyond the annotations.

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: verb, resource, scope, and payload contents in one pass. Nothing is redundant or misplaced.

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 tool is a simple read with full annotation coverage, a complete input schema, and an output schema, so the description need not explain return values. It is nearly complete, lacking only sibling differentiation from the other manifest-scoped 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%, including pointers to list_versions, list_scenarios, and list_platforms for the product, version, scenario, and environment parameters, so the schema carries the semantic burden. The description mentions none of these parameters and adds no meaning beyond what the schema already documents, making the 3 baseline 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?

The description gives a specific verb and resource ('Return the manifest of one recorded scenario') and names the manifest contents (step order, view, action, route transitions), so the purpose is clear. It does not, however, differentiate this from sibling manifest/read tools such as get_replay_manifest, get_application_manifest, or get_scenario_step, leaving the agent 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: 'one recorded scenario' signals that a scenario key is required, and the schema descriptions point at list_scenarios and list_versions for obtaining keys. There is no explicit statement about when to pick this over adjacent tools like get_scenario_scene or get_scenario_step, and no exclusions are given.

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