Skip to main content
Glama

List versions

list_versions
Read-onlyIdempotent

List versions newest first with their captured platform/environment pairs. Optionally filter by platform type and environment; never combine different versions.

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

Input Schema

NameRequiredDescriptionDefault
productYesProduct key, for example finance-ozon-ru
platformNoPlatform 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
resultYesResult entries

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / description
      Previous value: -"Structured result. Existing text or image content remains available in content."New value: +"Structured result wrapping a non-object value. The text content holds the same value unwrapped."
  2. Changed1 schema field changed
    • 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": {
      +      "description": "Result entries",
      +      "items": {
      +        "additionalProperties": true,
      +        "description": "Pinned capture version and captured variants",
      +        "properties": {
      +          "platforms": {
      +            "description": "Result entries",
      +            "items": {
      +              "additionalProperties": true,
      +              "description": "Captured platform/environment pair",
      +              "properties": {
      +                "environment": {
      +                  "description": "environment",
      +                  "type": "string"
      +                },
      +                "platform": {
      +                  "description": "platform",
      +                  "type": "string"
      +                }
      +              },
      +              "required": [
      +                "platform",
      +                "environment"
      +              ],
      +              "type": "object"
      +            },
      +            "type": "array"
      +          },
      +          "version": {
      +            "description": "Text value",
      +            "type": "string"
      +          }
      +        },
      +        "required": [
      +          "version",
      +          "platforms"
      +        ],
      +        "type": "object"
      +      },
      +      "type": "array"
      +    }
      +  },
      +  "required": [
      +    "result"
      +  ],
      +  "type": "object"
      +}
  3. 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 by structured data. The description adds the result ordering ("newest first") and a constraint about not combining versions, but that constraint is vague about what would go wrong, and no pagination or result-size behavior is mentioned. With annotations carrying the safety burden, 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.

Conciseness4/5

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

One compact sentence, front-loaded with the verb, resource, ordering and return content. The final clause "never combine different versions" is cryptic enough that it partially fails to earn its place, but the rest is waste-free.

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 exists, so return values need no explanation, and annotations cover safety. The description supplies ordering and filter intent, leaving only minor gaps around the meaning of the version-combination warning and pagination for a tool whose schema is fully documented.

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 docs are rich (they point at list_platforms.options.platforms[].id and explain when environment may be omitted). The description only restates that both filters are optional, adding no format or semantics 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?

The description gives a specific verb and resource ("List versions") plus the ordering and payload ("newest first with their captured platform/environment pairs"), so an agent knows exactly what comes back. It does not name or distinguish itself from near siblings such as get_version_metadata or list_version_files, which is the only thing keeping it from 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 Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

"Optionally filter by platform type and environment" implies the filtering use case, but there is no explicit when-to-use versus get_version_metadata or list_version_files, and no prerequisites stated. The trailing "never combine different versions" reads as a constraint but is not framed as an actionable usage rule.

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