Skip to main content
Glama

Reconstruct

by dev.reconstruct
OverviewDiscussionsAdmin

Get page stack

get_page_stack
Read-onlyIdempotent

Return stack.json beside a page capture for an exact stored view key and environment, when present.

Input Schema

NameRequiredDescriptionDefault
pageYesCaptured page key returned by list_pages or get_application_manifest, not a URL or filesystem path.
viewYesExact stored profile key from list_pages.views (desktop, mobile, numbered profiles or a device label); do not pass the operating system here.
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
resultYesDetected page technologies and stored source evidence

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedInput schema / properties / page / description
      Added value: +"Captured page key returned by list_pages or get_application_manifest, not a URL or filesystem path."
    • 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": {
+    "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 page technologies and stored source evidence",
+      "properties": {
+        "engine": {
+          "anyOf": [
+            {
+              "description": "Text value",
+              "type": "string"
+            },
+            {
+              "type": "null"
+            }
+          ]
+        },
+        "page": {
+          "description": "page",
+          "type": "string"
+        },
+        "product": {
+          "description": "product",
+          "type": "string"
+        },
+        "raw": {
+          "additionalProperties": true,
+          "description": "Original captured stack document",
+          "properties": {},
+          "type": "object"
+        },
+        "rendering": {
+          "anyOf": [
+            {
+              "$ref": "#/$defs/rendering"
+            },
+            {
+              "type": "null"
+            }
+          ]
+        },
+        "technologies": {
+          "description": "Result entries",
+          "items": {
+            "$ref": "#/$defs/technology"
+          },
+          "type": "array"
+        },
+        "version": {
+          "description": "version",
+          "type": "string"
+        },
+        "view": {
+          "description": "view",
+          "type": "string"
+        }
+      },
+      "required": [
+        "product",
+        "version",
+        "page",
+        "view",
+        "engine",
+        "rendering",
+        "technologies",
+        "raw"
+      ],
+      "type": "object"
+    }
+  },
+  "required": [
+    "result"
+  ],
+  "type": "object"
+}
  2. 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. The description adds only the 'when present' qualifier — useful, since the artifact may be absent — but does not say what an agent sees when it is absent (error vs empty result).

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 front-loaded sentence with no filler; the scope constraints are stated compactly. It earns its length, though the trailing 'when present' qualifier is the only piece of added information.

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-value explanation is not required, and the fully documented input schema carries parameter burden. The remaining gap is the absent-artifact behavior, which is not described.

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 all five parameters are already documented in the schema with sourcing guidance. The description only echoes the view/environment scoping, adding no syntax or format detail beyond the schema.

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 and resource: it returns stack.json for a page capture, scoped to a view key and environment. It is distinguishable from siblings like get_page_artifacts or get_page_bundles, though it never explicitly names an alternative to route against.

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?

The phrase 'for an exact stored view key and environment' and 'when present' implies the required context, but there is no explicit when-to-use / when-not-to-use guidance and no named alternative for agents that need other page artifacts.

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