Skip to main content
Glama

Reconstruct

by dev.reconstruct
OverviewDiscussionsAdmin

Get technology stack

get_technology_stack
Read-onlyIdempotent

Return the detected technology stack and rendering mode for a product version on a platform (from stack.json).

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
resultYesDetected technology stack and rendering mode

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: +{
+  "$defs": {
+    "rendering": {
+      "additionalProperties": true,
+      "description": "Detected rendering mode",
+      "properties": {
+        "confidence": {
+          "description": "Count or zero-based index",
+          "type": "integer"
+        },
+        "framework": {
+          "anyOf": [
+            {
+              "description": "Text value",
+              "type": "string"
+            },
+            {
+              "type": "null"
+            }
+          ]
+        },
+        "mode": {
+          "description": "Text value",
+          "type": "string"
+        },
+        "signals": {
+          "description": "Result entries",
+          "items": {
+            "description": "Text value",
+            "type": "string"
+          },
+          "type": "array"
+        }
+      },
+      "required": [
+        "mode",
+        "confidence",
+        "framework",
+        "signals"
+      ],
+      "type": "object"
+    },
+    "technology": {
+      "additionalProperties": true,
+      "description": "Detected frontend technology",
+      "properties": {
+        "categories": {
+          "description": "Result entries",
+          "items": {
+            "description": "Text value",
+            "type": "string"
+          },
+          "type": "array"
+        },
+        "confidence": {
+          "description": "Count or zero-based index",
+          "type": "integer"
+        },
+        "name": {
+          "description": "Text value",
+          "type": "string"
+        },
+        "primaryCategory": {
+          "anyOf": [
+            {
+              "description": "Text value",
+              "type": "string"
+            },
+            {
+              "type": "null"
+            }
+          ]
+        },
+        "version": {
+          "anyOf": [
+            {
+              "description": "Text value",
+              "type": "string"
+            },
+            {
+              "type": "null"
+            }
+          ]
+        }
+      },
+      "required": [
+        "name",
+        "version",
+        "confidence",
+        "primaryCategory",
+        "categories"
+      ],
+      "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": "Detected technology stack and rendering mode",
+      "properties": {
+        "aggregatedAt": {
+          "anyOf": [
+            {
+              "description": "Text value",
+              "type": "string"
+            },
+            {
+              "type": "null"
+            }
+          ]
+        },
+        "engine": {
+          "anyOf": [
+            {
+              "description": "Text value",
+              "type": "string"
+            },
+            {
+              "type": "null"
+            }
+          ]
+        },
+        "environment": {
+          "description": "environment",
+          "type": "string"
+        },
+        "platform": {
+          "description": "platform",
+          "type": "string"
+        },
+        "product": {
+          "description": "product",
+          "type": "string"
+        },
+        "rendering": {
+          "anyOf": [
+            {
+              "$ref": "#/$defs/rendering"
+            },
+            {
+              "type": "null"
+            }
+          ]
+        },
+        "technologies": {
+          "description": "Result entries",
+          "items": {
+            "$ref": "#/$defs/technology"
+          },
+          "type": "array"
+        },
+        "version": {
+          "description": "version",
+          "type": "string"
+        }
+      },
+      "required": [
+        "product",
+        "platform",
+        "environment",
+        "version",
+        "engine",
+        "aggregatedAt",
+        "rendering",
+        "technologies"
+      ],
+      "type": "object"
+    }
+  },
+  "required": [
+    "result"
+  ],
+  "type": "object"
+}
  2. 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 settled. The description adds modest value by naming the data source (stack.json) and indicating the returned shape (stack plus rendering mode), but says nothing about failure modes when a version/platform combination lacks a captured stack.

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?

A single efficient sentence with the resource and scope front-loaded and no filler. Only the parenthetical source note is mildly secondary, but nothing is wasted.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/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 not be described, and annotations cover the safety profile. What is missing is usage context: how this product-version stack differs from the page-level stack sibling, which an agent must infer from names alone given the dense sibling list.

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 all four parameters in depth, including cross-references to list_versions and list_platforms. The description adds no parameter-level meaning beyond restating the required product/version/platform scope, which is the baseline-3 case.

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 (detected technology stack and rendering mode) scoped to a product version on a platform, and discloses its underlying source (stack.json). It is clearly distinct from the page-level sibling get_page_stack, but it does not name or route against any sibling explicitly.

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 gives no when-to-use or when-not-to-use guidance. It does not explain how this differs from get_page_stack or get_version_metadata, nor does it state prerequisites such as needing a version pinned from list_versions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Reconstruct toolsInspect
Try in Browser
Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources