Reconstruct

List component candidates

list_component_candidates

Read-onlyIdempotent

List candidate visual components in a page viewport. IDs are element indexes; candidates are heuristic, not verified reusable UI components.

Input Schema

Name	Required	Description
`page`	Yes	Captured page key returned by list_pages or get_application_manifest, not a URL or filesystem path.
`view`	Yes	Exact stored profile key from list_pages.views (desktop, mobile, numbered profiles or a device label); do not pass the operating system here.
`limit`	No	Maximum items returned, clamped to 1..200. Default 100.
`product`	Yes	Product key, for example finance-ozon-ru
`version`	Yes	Exact capture version returned by list_versions. Pin the same version across related calls; do not use latest as an alias.
`environment`	No	Environment 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

Name	Required	Description	Default
`result`	Yes	Result entries

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedOct 12, 2026

addedInput schema / properties / limit / description

Added value: +"Maximum items returned, clamped to 1..200. Default 100."

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": {
+    "rect": {
+      "additionalProperties": true,
+      "description": "Captured CSS-pixel rectangle",
+      "properties": {
+        "height": {
+          "description": "height",
+          "type": "number"
+        },
+        "width": {
+          "description": "width",
+          "type": "number"
+        },
+        "x": {
+          "description": "x",
+          "type": "number"
+        },
+        "y": {
+          "description": "y",
+          "type": "number"
+        }
+      },
+      "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": {
+      "description": "Result entries",
+      "items": {
+        "additionalProperties": true,
+        "description": "Candidate visual region",
+        "properties": {
+          "id": {
+            "description": "Count or zero-based index",
+            "type": "integer"
+          },
+          "label": {
+            "description": "Text value",
+            "type": "string"
+          },
+          "rect": {
+            "anyOf": [
+              {
+                "$ref": "#/$defs/rect"
+              },
+              {
+                "type": "null"
+              }
+            ]
+          },
+          "tag": {
+            "anyOf": [
+              {
+                "description": "Text value",
+                "type": "string"
+              },
+              {
+                "type": "null"
+              }
+            ]
+          }
+        },
+        "required": [
+          "id",
+          "tag",
+          "label",
+          "rect"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "result"
+  ],
+  "type": "object"
+}

First observedOct 12, 2026

TDQS

A3.6/5.0

Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the safety profile is covered. The description adds genuine non-annotation context: the returned IDs are element indexes, and results are heuristic rather than verified reusable components — a reliability caveat that directly affects how an agent should treat the output. Return shape is covered by the output schema.

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, purpose front-loaded, with the reliability caveat immediately after. No filler or repetition of schema content.

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 annotations covering safety and an output schema covering return values, the description's job is mostly purpose plus caveats, and it handles the caveat well. It is slightly thin on prerequisite chaining (which list_* call supplies page/view/version) and on sibling routing for a 6-parameter tool.

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 every parameter (page, view, limit, product, version, environment) is already fully documented in the schema with constraints and sourcing hints. The description adds no parameter-level detail, 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?

States a specific verb+resource ('List candidate visual components in a page viewport') and adds a qualifying clause ('candidates are heuristic, not verified reusable UI components') that meaningfully separates it from the verified-component siblings like get_page_components and get_component. It does not name those siblings, so it falls short of a 5.

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?

There is no explicit when-to-use, when-not-to-use, or alternative named ('use this to discover, then call get_component to verify'). The 'heuristic, not verified' clause hints at a discovery role, but an agent gets no routing guidance among the many component-related siblings. Comparable to the calibration example that scored 2 for absent usage guidance.

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

All Reconstruct tools Inspect

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

Need Help?