Skip to main content
Glama

Reconstruct

by dev.reconstruct
OverviewDiscussionsAdmin

Get page transitions

get_page_transitions
Read-onlyIdempotent

List links discovered on a captured route and resolve links to captured route names. These are potential transitions, not observed clicks.

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.
limitNoMaximum items returned, clamped to 1..200. Default 100.
offsetNoZero-based result offset for pagination. Negative values are treated as zero; default is 0.
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
resultYesDiscovered links, not observed navigation events

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changed
    • addedInput schema / properties / limit / description
      Added value: +"Maximum items returned, clamped to 1..200. Default 100."
    • addedInput schema / properties / offset / description
      Added value: +"Zero-based result offset for pagination. Negative values are treated as zero; default is 0."
    • 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": "Discovered links, not observed navigation events",
+      "properties": {
+        "total": {
+          "description": "Count or zero-based index",
+          "type": "integer"
+        },
+        "transitions": {
+          "description": "Result entries",
+          "items": {
+            "additionalProperties": true,
+            "description": "Potential link transition",
+            "properties": {
+              "clickObserved": {
+                "description": "Whether this condition holds",
+                "type": "boolean"
+              },
+              "href": {
+                "description": "Text value",
+                "type": "string"
+              },
+              "kind": {
+                "description": "Text value",
+                "type": "string"
+              },
+              "targetPage": {
+                "anyOf": [
+                  {
+                    "description": "Text value",
+                    "type": "string"
+                  },
+                  {
+                    "type": "null"
+                  }
+                ]
+              }
+            },
+            "required": [
+              "href",
+              "targetPage",
+              "kind",
+              "clickObserved"
+            ],
+            "type": "object"
+          },
+          "type": "array"
+        }
+      },
+      "required": [
+        "total",
+        "transitions"
+      ],
+      "type": "object"
+    }
+  },
+  "required": [
+    "result"
+  ],
+  "type": "object"
+}
  2. First observed

TDQS

A3.8/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint/idempotentHint and destructiveHint=false, so safety is covered. The description adds genuine semantic context beyond annotations: results are potential (discovered) transitions rather than observed navigation events, which tells the agent what the data does and does not represent.

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 tight sentences, zero filler; the core action is front-loaded and the disambiguating scope note follows immediately. Every sentence earns its place.

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, full schema coverage, and annotations, the description only needs to convey scope and semantics, which it does. Minor gap: it speaks of a 'captured route' while the required parameter is a captured 'page' key, and a route-oriented sibling exists, so an agent may want one word tying the two vocabularies together.

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 seven parameters (page, view, version, product, environment, limit, offset) are already documented with format and provenance guidance. The description adds no parameter-level meaning, so the baseline of 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?

States a concrete verb+resource: lists links discovered on a captured route and resolves them to captured route names. The clarifying line 'potential transitions, not observed clicks' distinguishes it from click-observation siblings, but no sibling such as get_route_tree is named for contrast.

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?

Usage is only implied — an agent can infer you call this to enumerate outgoing links for a page/route. There is no explicit when-to-use, when-not-to-use, or alternative (e.g., get_route_tree, list_pages) called out, so selection still requires inference.

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