Skip to main content
Glama

Get version metadata

get_version_metadata
Read-onlyIdempotent

Return version.json metadata for a product version on a platform (product, version, source, capturedAt, duration, and artifact pointers).

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>",
      "platform": "<platform>",
      "version": "<version>"
    },
    "name": "get_version_metadata"
  }
}

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.
platformYesPlatform type ID from list_platforms.options.platforms[].id (backend CatalogPlatform.view). Use backend IDs verbatim; desktop/mobile are current examples. Environment is selected separately.
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
productYesproduct
versionYesversion
metadataYesCapture metadata; available fields depend on archive version
platformYesplatform
environmentYesenvironment

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed9 schema fields changed
    • 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 capture version metadata"
    • addedOutput schema / properties / environment
      Added value: +{
      +  "description": "environment",
      +  "type": "string"
      +}
    • addedOutput schema / properties / metadata
      Added value: +{
      +  "additionalProperties": true,
      +  "description": "Capture metadata; available fields depend on archive version",
      +  "properties": {
      +    "capturedAt": {
      +      "anyOf": [
      +        {
      +          "description": "capturedAt",
      +          "type": "string"
      +        },
      +        {
      +          "type": "null"
      +        }
      +      ]
      +    },
      +    "environment": {
      +      "anyOf": [
      +        {
      +          "description": "environment",
      +          "type": "string"
      +        },
      +        {
      +          "type": "null"
      +        }
      +      ]
      +    },
      +    "platform": {
      +      "anyOf": [
      +        {
      +          "description": "platform",
      +          "type": "string"
      +        },
      +        {
      +          "type": "null"
      +        }
      +      ]
      +    },
      +    "source": {
      +      "anyOf": [
      +        {
      +          "description": "source",
      +          "type": "string"
      +        },
      +        {
      +          "type": "null"
      +        }
      +      ]
      +    }
      +  },
      +  "type": "object"
      +}
    • addedOutput schema / properties / platform
      Added value: +{
      +  "description": "platform",
      +  "type": "string"
      +}
    • addedOutput schema / properties / product
      Added value: +{
      +  "description": "product",
      +  "type": "string"
      +}
    • removedOutput schema / properties / result
      Removed value: -{
      -  "additionalProperties": true,
      -  "description": "Stored capture version metadata",
      -  "properties": {
      -    "environment": {
      -      "description": "environment",
      -      "type": "string"
      -    },
      -    "metadata": {
      -      "additionalProperties": true,
      -      "description": "Capture metadata; available fields depend on archive version",
      -      "properties": {
      -        "capturedAt": {
      -          "anyOf": [
      -            {
      -              "description": "capturedAt",
      -              "type": "string"
      -            },
      -            {
      -              "type": "null"
      -            }
      -          ]
      -        },
      -        "environment": {
      -          "anyOf": [
      -            {
      -              "description": "environment",
      -              "type": "string"
      -            },
      -            {
      -              "type": "null"
      -            }
      -          ]
      -        },
      -        "platform": {
      -          "anyOf": [
      -            {
      -              "description": "platform",
      -              "type": "string"
      -            },
      -            {
      -              "type": "null"
      -            }
      -          ]
      -        },
      -        "source": {
      -          "anyOf": [
      -            {
      -              "description": "source",
      -              "type": "string"
      -            },
      -            {
      -              "type": "null"
      -            }
      -          ]
      -        }
      -      },
      -      "type": "object"
      -    },
      -    "platform": {
      -      "description": "platform",
      -      "type": "string"
      -    },
      -    "product": {
      -      "description": "product",
      -      "type": "string"
      -    },
      -    "version": {
      -      "description": "version",
      -      "type": "string"
      -    }
      -  },
      -  "required": [
      -    "product",
      -    "platform",
      -    "environment",
      -    "version",
      -    "metadata"
      -  ],
      -  "type": "object"
      -}
    • addedOutput schema / properties / version
      Added value: +{
      +  "description": "version",
      +  "type": "string"
      +}
    • changedOutput schema / required
      Previous value: -[
      -  "result"
      -]New value: +[
      +  "product",
      +  "platform",
      +  "environment",
      +  "version",
      +  "metadata"
      +]
  2. Changed2 schema fields changed
    • 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: +{
      +  "$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": "Stored capture version metadata",
      +      "properties": {
      +        "environment": {
      +          "description": "environment",
      +          "type": "string"
      +        },
      +        "metadata": {
      +          "additionalProperties": true,
      +          "description": "Capture metadata; available fields depend on archive version",
      +          "properties": {
      +            "capturedAt": {
      +              "anyOf": [
      +                {
      +                  "description": "capturedAt",
      +                  "type": "string"
      +                },
      +                {
      +                  "type": "null"
      +                }
      +              ]
      +            },
      +            "environment": {
      +              "anyOf": [
      +                {
      +                  "description": "environment",
      +                  "type": "string"
      +                },
      +                {
      +                  "type": "null"
      +                }
      +              ]
      +            },
      +            "platform": {
      +              "anyOf": [
      +                {
      +                  "description": "platform",
      +                  "type": "string"
      +                },
      +                {
      +                  "type": "null"
      +                }
      +              ]
      +            },
      +            "source": {
      +              "anyOf": [
      +                {
      +                  "description": "source",
      +                  "type": "string"
      +                },
      +                {
      +                  "type": "null"
      +                }
      +              ]
      +            }
      +          },
      +          "type": "object"
      +        },
      +        "platform": {
      +          "description": "platform",
      +          "type": "string"
      +        },
      +        "product": {
      +          "description": "product",
      +          "type": "string"
      +        },
      +        "version": {
      +          "description": "version",
      +          "type": "string"
      +        }
      +      },
      +      "required": [
      +        "product",
      +        "platform",
      +        "environment",
      +        "version",
      +        "metadata"
      +      ],
      +      "type": "object"
      +    }
      +  },
      +  "required": [
      +    "result"
      +  ],
      +  "type": "object"
      +}
  3. First observed

TDQS

B3.2/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 value by disclosing the shape of the payload (source, capturedAt, duration, artifact pointers), but says nothing about failure modes (missing version or environment) or size/availability caveats.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One front-loaded sentence with no filler. The parenthetical field list is largely redundant with the existing output schema, which keeps it just below a 5.

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-only metadata getter with a fully documented four-parameter schema, an output schema, and clear annotations, so the short description is close to sufficient. The remaining gap is sibling disambiguation against list_versions, list_version_files, and the manifest getters.

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 parameter descriptions are unusually strong, including the warning not to use 'latest' and how to source platform/environment IDs. The description itself adds no parameter meaning beyond restating the three required fields, so the schema is doing all the work and the baseline of 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 gives a specific verb and resource ("Return version.json metadata for a product version on a platform") and enumerates the returned fields (product, version, source, capturedAt, duration, artifact pointers), so the agent knows exactly what it fetches. It does not explicitly name how it differs from near-siblings such as get_version_files or list_versions, so it falls short of a 5.

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?

The description contains no when-to-use or when-not-to-use guidance and names no alternatives. The only routing hints ('version returned by list_versions', 'Platform type ID from list_platforms') live in the schema's parameter descriptions, not in the tool description itself.

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