Skip to main content
Glama

Reconstruct

by dev.reconstruct
OverviewDiscussionsAdmin

Get page regions

get_page_regions
Read-onlyIdempotent

Map a page into viewport-height bands with y bounds, element counts, and heading previews. Prefer get_page_outline regions (bundleTarget=true) over viewport bands; use regionIndex only when banding by viewport, not for micro-sections.

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
resultYesViewport-sized regions of the captured page

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: +{
+  "$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": "Viewport-sized regions of the captured page",
+      "properties": {
+        "regions": {
+          "description": "Result entries",
+          "items": {
+            "additionalProperties": true,
+            "description": "Viewport region",
+            "properties": {
+              "elementCount": {
+                "description": "Count or zero-based index",
+                "type": "integer"
+              },
+              "headings": {
+                "description": "Result entries",
+                "items": {
+                  "description": "Text value",
+                  "type": "string"
+                },
+                "type": "array"
+              },
+              "index": {
+                "description": "Count or zero-based index",
+                "type": "integer"
+              },
+              "yEnd": {
+                "description": "Measured value",
+                "type": "number"
+              },
+              "yStart": {
+                "description": "Measured value",
+                "type": "number"
+              }
+            },
+            "required": [
+              "index",
+              "yStart",
+              "yEnd",
+              "elementCount",
+              "headings"
+            ],
+            "type": "object"
+          },
+          "type": "array"
+        },
+        "scrollHeight": {
+          "description": "Measured value",
+          "type": "number"
+        },
+        "truncated": {
+          "description": "Whether this condition holds",
+          "type": "boolean"
+        },
+        "viewportHeight": {
+          "description": "Measured value",
+          "type": "number"
+        }
+      },
+      "required": [
+        "viewportHeight",
+        "scrollHeight",
+        "truncated",
+        "regions"
+      ],
+      "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/idempotentHint/destructiveHint=false, so safety is covered. The description adds the shape of the banding output, which is useful, but discloses nothing about cost, granularity limits, or side effects beyond what annotations and the output schema supply.

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?

Two tight sentences with the core purpose front-loaded and no filler. The second sentence is dense with undefined terms (bundleTarget, regionIndex), which costs a little clarity but not length.

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 needn't be spelled out, and the description still sketches them. For a 5-parameter read tool with full schema coverage and annotations, this is close to complete; only the undefined regionIndex/bundleTarget vocabulary leaves a small gap.

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 each parameter (page, view, product, version, environment) is already documented with usage warnings in the schema. The description contributes no additional parameter meaning, 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?

Specific verb+resource: 'Map a page into viewport-height bands', plus the concrete payload of those bands (y bounds, element counts, heading previews). It also names the sibling get_page_outline regions and contrasts itself with it, so the agent can distinguish the two.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

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

Explicitly routes the agent: prefer get_page_outline with bundleTarget=true, and reserve regionIndex for viewport banding rather than micro-sections. That is real when-to-use guidance naming an alternative, though the conditions ('bundleTarget=true', 'micro-sections') are not defined anywhere in the schema.

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