Skip to main content
Glama

Reconstruct

by dev.reconstruct
OverviewDiscussionsAdmin

List product requests

list_product_requests
Read-only

List product requests, newest first. scope=mine (default) returns your requests; scope=public returns other users' requests with only public fields, omitting owner identity, private details and safety/review notes. Follow nextPageToken with pageToken and the same scope. pageSize defaults to 50 and is capped at 200. Capture progress is exposed without job IDs.

Input Schema

NameRequiredDescriptionDefault
scopeNomine (default) returns your requests; public returns other users public requests with private and safety details omitted.mine
pageSizeNoMaximum requests per page. Default 50; values at or below zero use 50 and values above 200 are capped at 200.
pageTokenNoOpaque nextPageToken from the previous list_product_requests result. Default empty starts the first page; retain the same scope.

Output Schema

NameRequiredDescriptionDefault
resultYesRequests for the selected scope and continuation token

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedInput schema / properties / pageSize / description
      Added value: +"Maximum requests per page. Default 50; values at or below zero use 50 and values above 200 are capped at 200."
    • addedInput schema / properties / pageToken / description
      Added value: +"Opaque nextPageToken from the previous list_product_requests result. Default empty starts the first page; retain the same scope."
    • addedInput schema / properties / scope / description
      Added value: +"mine (default) returns your requests; public returns other users public requests with private and safety details omitted."
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$defs": {
+    "privateRequest": {
+      "additionalProperties": false,
+      "description": "Authenticated owner request including review and capture progress",
+      "properties": {
+        "createdAt": {
+          "description": "ISO-8601 timestamp",
+          "type": "string"
+        },
+        "history": {
+          "description": "Result entries",
+          "items": {
+            "$ref": "#/$defs/requestHistory"
+          },
+          "type": "array"
+        },
+        "jobStatus": {
+          "description": "jobStatus",
+          "type": "string"
+        },
+        "payloadJson": {
+          "description": "payloadJson",
+          "type": "string"
+        },
+        "product": {
+          "description": "product",
+          "type": "string"
+        },
+        "progressStatus": {
+          "description": "progressStatus",
+          "type": "string"
+        },
+        "requestId": {
+          "description": "requestId",
+          "type": "string"
+        },
+        "requestType": {
+          "description": "requestType",
+          "type": "string"
+        },
+        "reviewedAt": {
+          "anyOf": [
+            {
+              "description": "ISO-8601 timestamp",
+              "type": "string"
+            },
+            {
+              "type": "null"
+            }
+          ]
+        },
+        "safetyStatus": {
+          "description": "safetyStatus",
+          "type": "string"
+        },
+        "status": {
+          "description": "status",
+          "type": "string"
+        },
+        "subject": {
+          "description": "subject",
+          "type": "string"
+        },
+        "url": {
+          "description": "url",
+          "type": "string"
+        },
+        "workflowStatus": {
+          "description": "workflowStatus",
+          "type": "string"
+        }
+      },
+      "required": [
+        "requestId",
+        "requestType",
+        "product",
+        "subject",
+        "url",
+        "status",
+        "payloadJson",
+        "createdAt",
+        "history",
+        "safetyStatus",
+        "workflowStatus",
+        "jobStatus",
+        "progressStatus",
+        "reviewedAt"
+      ],
+      "type": "object"
+    },
+    "publicRequest": {
+      "additionalProperties": false,
+      "description": "Other user public request with private review/safety fields omitted",
+      "properties": {
+        "createdAt": {
+          "description": "ISO-8601 timestamp",
+          "type": "string"
+        },
+        "history": {
+          "description": "Result entries",
+          "items": {
+            "$ref": "#/$defs/requestHistory"
+          },
+          "type": "array"
+        },
+        "payloadJson": {
+          "description": "payloadJson",
+          "type": "string"
+        },
+        "product": {
+          "description": "product",
+          "type": "string"
+        },
+        "requestId": {
+          "description": "requestId",
+          "type": "string"
+        },
+        "requestType": {
+          "description": "requestType",
+          "type": "string"
+        },
+        "status": {
+          "description": "status",
+          "type": "string"
+        },
+        "subject": {
+          "description": "subject",
+          "type": "string"
+        },
+        "url": {
+          "description": "url",
+          "type": "string"
+        }
+      },
+      "required": [
+        "requestId",
+        "requestType",
+        "product",
+        "subject",
+        "url",
+        "status",
+        "payloadJson",
+        "createdAt",
+        "history"
+      ],
+      "type": "object"
+    },
+    "request": {
+      "anyOf": [
+        {
+          "$ref": "#/$defs/privateRequest"
+        },
+        {
+          "$ref": "#/$defs/publicRequest"
+        }
+      ],
+      "description": "Request fields vary with mine/public scope"
+    },
+    "requestHistory": {
+      "additionalProperties": true,
+      "description": "Public workflow transition",
+      "properties": {
+        "actor": {
+          "description": "actor",
+          "type": "string"
+        },
+        "at": {
+          "description": "ISO-8601 timestamp",
+          "type": "string"
+        },
+        "reason": {
+          "description": "reason",
+          "type": "string"
+        },
+        "status": {
+          "description": "status",
+          "type": "string"
+        }
+      },
+      "required": [
+        "status",
+        "reason",
+        "actor",
+        "at"
+      ],
+      "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": "Requests for the selected scope and continuation token",
+      "properties": {
+        "nextPageToken": {
+          "description": "Empty string when no further page exists",
+          "type": "string"
+        },
+        "requests": {
+          "description": "Result entries",
+          "items": {
+            "$ref": "#/$defs/request"
+          },
+          "type": "array"
+        }
+      },
+      "required": [
+        "requests",
+        "nextPageToken"
+      ],
+      "type": "object"
+    }
+  },
+  "required": [
+    "result"
+  ],
+  "type": "object"
+}
  2. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations only supply readOnlyHint=true, so the description carries the rest: it discloses that scope=public omits owner identity, private details, and safety/review notes, that ordering is newest-first, that pageSize is capped at 200, and that capture progress is surfaced without job IDs. These are real visibility and pagination behaviors beyond the annotation, though auth requirements and rate limits are unstated.

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?

Four tight sentences, front-loaded with purpose and ordering before visibility rules and pagination. Nearly every sentence earns its place, though the closing "Capture progress is exposed without job IDs" is cryptic enough to need a second read.

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 unnecessary, and the description covers scope semantics, ordering, page-size bounds, and the token-following loop needed to page correctly. Only minor gaps remain, such as total-count or empty-result behavior, which are low-impact for a list 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 all three parameters (scope, pageSize, pageToken) are already documented with defaults and cap semantics. The description largely restates the same scope and pageSize facts and adds only the small operational note that the same scope must be reused with pageToken. Baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ("List product requests") plus the ordering guarantee ("newest first"), which immediately separates it from get_product_request (single fetch) and create_product_request (write) among the siblings. An agent can pick this tool without opening any schema.

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?

Gives clear conditional guidance: scope=mine for your own requests, scope=public for other users' public view, and explicitly instructs to follow nextPageToken with pageToken "and the same scope." It does not name sibling alternatives such as get_product_request for a single item, so it stops short of full when/when-not routing.

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