Skip to main content
Glama

Get platform summary

get_platform_summary
Read-onlyIdempotent

Summarize a selected product version, platform type and environment: page count and available stack, languages, media, fonts, themes, routes and recordings. For multiple environments, specify environment from list_versions.

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
resultYesAvailability summary for the selected capture

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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": "Availability summary for the selected capture",
      +      "properties": {
      +        "available": {
      +          "description": "Result entries",
      +          "items": {
      +            "description": "Suggested tool name",
      +            "type": "string"
      +          },
      +          "type": "array"
      +        },
      +        "capturedAt": {
      +          "anyOf": [
      +            {
      +              "description": "capturedAt",
      +              "type": "string"
      +            },
      +            {
      +              "type": "null"
      +            }
      +          ]
      +        },
      +        "environment": {
      +          "description": "environment",
      +          "type": "string"
      +        },
      +        "fileCount": {
      +          "description": "fileCount",
      +          "type": "integer"
      +        },
      +        "hasAssets": {
      +          "description": "hasAssets",
      +          "type": "boolean"
      +        },
      +        "hasClickCapture": {
      +          "description": "hasClickCapture",
      +          "type": "boolean"
      +        },
      +        "hasFonts": {
      +          "description": "hasFonts",
      +          "type": "boolean"
      +        },
      +        "hasLanguages": {
      +          "description": "hasLanguages",
      +          "type": "boolean"
      +        },
      +        "hasReplays": {
      +          "description": "hasReplays",
      +          "type": "boolean"
      +        },
      +        "hasRoutes": {
      +          "description": "hasRoutes",
      +          "type": "boolean"
      +        },
      +        "hasStack": {
      +          "description": "hasStack",
      +          "type": "boolean"
      +        },
      +        "hasThemes": {
      +          "description": "hasThemes",
      +          "type": "boolean"
      +        },
      +        "pageCount": {
      +          "description": "pageCount",
      +          "type": "integer"
      +        },
      +        "platform": {
      +          "description": "platform",
      +          "type": "string"
      +        },
      +        "product": {
      +          "description": "product",
      +          "type": "string"
      +        },
      +        "source": {
      +          "anyOf": [
      +            {
      +              "description": "source",
      +              "type": "string"
      +            },
      +            {
      +              "type": "null"
      +            }
      +          ]
      +        },
      +        "version": {
      +          "description": "version",
      +          "type": "string"
      +        }
      +      },
      +      "required": [
      +        "product",
      +        "platform",
      +        "environment",
      +        "version",
      +        "capturedAt",
      +        "source",
      +        "pageCount",
      +        "fileCount",
      +        "hasStack",
      +        "hasLanguages",
      +        "hasAssets",
      +        "hasFonts",
      +        "hasThemes",
      +        "hasClickCapture",
      +        "hasRoutes",
      +        "hasReplays",
      +        "available"
      +      ],
      +      "type": "object"
      +    }
      +  },
      +  "required": [
      +    "result"
      +  ],
      +  "type": "object"
      +}
  2. 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. The description adds the cross-product/platform/environment scope and the multi-environment caveat, but says nothing about cost, aggregation breadth, or whether an environment-less call silently picks a default.

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?

Two sentences, front-loaded with the scope and then the environment caveat. The output enumeration is dense but each item earns its place by telling the agent what the summary actually contains.

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?

With an output schema present, return values need no explanation, and the description adequately covers what is aggregated and how environment selection works. It is slightly thin on prerequisites for the required version/platform values, but the schema descriptions carry those.

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 schema already documents product, version, platform and environment in detail; baseline 3 applies. The description restates the environment hint ('specify environment from list_versions') but does not resolve the apparent source discrepancy with the schema, which points to list_platforms for environment IDs.

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 (summarize) and resource (product version + platform + environment) and enumerates the summarizable dimensions: page count, stack, languages, media, fonts, themes, routes, recordings. That enumeration lets an agent distinguish it from narrower siblings like get_page_summary or get_version_metadata, though no sibling is named explicitly.

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?

Only actionable guidance is the conditional 'For multiple environments, specify environment from list_versions,' which addresses the optional parameter. There is no statement of when to prefer this aggregate summary over siblings such as get_version_metadata, get_page_summary, or get_technology_stack, leaving usage largely implied.

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