Skip to main content
Glama

Get application manifest

get_application_manifest
Read-onlyIdempotent

Return the complete route inventory for a captured application version, including desktop/mobile availability and stage names.

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.
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
resultYesCapture application inventory

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / product / description
      Added value: +"Product key, for example finance-ozon-ru"
    • 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": {
      +    "pageEntry": {
      +      "additionalProperties": true,
      +      "description": "Captured page inventory entry",
      +      "properties": {
      +        "desktop": {
      +          "description": "Whether this condition holds",
      +          "type": "boolean"
      +        },
      +        "error": {
      +          "anyOf": [
      +            {
      +              "description": "Text value",
      +              "type": "string"
      +            },
      +            {
      +              "type": "null"
      +            }
      +          ]
      +        },
      +        "mobile": {
      +          "description": "Whether this condition holds",
      +          "type": "boolean"
      +        },
      +        "name": {
      +          "description": "name",
      +          "type": "string"
      +        },
      +        "url": {
      +          "anyOf": [
      +            {
      +              "description": "Text value",
      +              "type": "string"
      +            },
      +            {
      +              "type": "null"
      +            }
      +          ]
      +        },
      +        "views": {
      +          "description": "Result entries",
      +          "items": {
      +            "$ref": "#/$defs/view"
      +          },
      +          "type": "array"
      +        }
      +      },
      +      "required": [
      +        "name",
      +        "views",
      +        "url",
      +        "error",
      +        "desktop",
      +        "mobile"
      +      ],
      +      "type": "object"
      +    },
      +    "view": {
      +      "additionalProperties": true,
      +      "description": "Stored view profile and captured platform/environment",
      +      "properties": {
      +        "environment": {
      +          "description": "Text value",
      +          "type": "string"
      +        },
      +        "platform": {
      +          "anyOf": [
      +            {
      +              "description": "Text value",
      +              "type": "string"
      +            },
      +            {
      +              "type": "null"
      +            }
      +          ]
      +        },
      +        "view": {
      +          "description": "Text value",
      +          "type": "string"
      +        }
      +      },
      +      "required": [
      +        "view",
      +        "platform",
      +        "environment"
      +      ],
      +      "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": {
      +      "additionalProperties": true,
      +      "description": "Capture application inventory",
      +      "properties": {
      +        "capturedAt": {
      +          "anyOf": [
      +            {
      +              "description": "Text value",
      +              "type": "string"
      +            },
      +            {
      +              "type": "null"
      +            }
      +          ]
      +        },
      +        "environment": {
      +          "description": "environment",
      +          "type": "string"
      +        },
      +        "interactionEvents": {
      +          "description": "Text value",
      +          "type": "string"
      +        },
      +        "product": {
      +          "description": "product",
      +          "type": "string"
      +        },
      +        "replays": {
      +          "description": "Result entries",
      +          "items": {
      +            "anyOf": [
      +              {
      +                "description": "Text value",
      +                "type": "string"
      +              },
      +              {
      +                "type": "null"
      +              }
      +            ]
      +          },
      +          "type": "array"
      +        },
      +        "routeCount": {
      +          "description": "Count or zero-based index",
      +          "type": "integer"
      +        },
      +        "routes": {
      +          "description": "Result entries",
      +          "items": {
      +            "$ref": "#/$defs/pageEntry"
      +          },
      +          "type": "array"
      +        },
      +        "scenarios": {
      +          "description": "Result entries",
      +          "items": {
      +            "anyOf": [
      +              {
      +                "description": "Text value",
      +                "type": "string"
      +              },
      +              {
      +                "type": "null"
      +              }
      +            ]
      +          },
      +          "type": "array"
      +        },
      +        "stages": {
      +          "description": "Result entries",
      +          "items": {
      +            "anyOf": [
      +              {
      +                "description": "Text value",
      +                "type": "string"
      +              },
      +              {
      +                "type": "null"
      +              }
      +            ]
      +          },
      +          "type": "array"
      +        },
      +        "version": {
      +          "description": "version",
      +          "type": "string"
      +        }
      +      },
      +      "required": [
      +        "product",
      +        "version",
      +        "environment",
      +        "capturedAt",
      +        "routeCount",
      +        "routes",
      +        "stages",
      +        "scenarios",
      +        "replays",
      +        "interactionEvents"
      +      ],
      +      "type": "object"
      +    }
      +  },
      +  "required": [
      +    "result"
      +  ],
      +  "type": "object"
      +}
  2. First observed

TDQS

B3.4/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 structurally. The description adds useful content scope (availability plus stage names) but says nothing about version-pinning discipline, completeness guarantees, or any cross-call consistency requirement.

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 that names the resource, its scope and the notable fields with zero filler.

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?

An output schema and full annotation coverage exist, so the description need not explain returns or safety. What it provides is sufficient for a read-only manifest fetch, though it omits any hint about when this manifest should be preferred over the closely named alternatives.

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 itself carries rich semantics, including the explicit 'do not use latest as an alias' warning and the environment-omission rule. The description adds no parameter meaning beyond the schema, 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?

States a specific verb ('Return') and resource ('complete route inventory for a captured application version') plus scope detail (desktop/mobile availability, stage names). It is clear on its own, but it never distinguishes itself from semantically adjacent siblings like get_route_tree, get_replay_manifest, or get_scenario_manifest.

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?

No when-to-use guidance, prerequisites, or alternatives are given despite the presence of several manifest/route siblings. The agent must infer context entirely from 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