Skip to main content
Glama

SupplySlate

by com.supplyslate
OverviewDiscussionsAdmin

list_orders

Read-onlyIdempotent

List merchant-confirmed orders for the buyer organization. A plan or queued handoff is never represented as an order.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataYes
summaryYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedOutput schema / properties / summary
      Added value: +{
+  "additionalProperties": false,
+  "properties": {
+    "total_orders": {
+      "maximum": 9007199254740991,
+      "minimum": 0,
+      "type": "integer"
+    }
+  },
+  "required": [
+    "total_orders"
+  ],
+  "type": "object"
+}
    • changedOutput schema / required
      Previous value: -[
-  "data"
-]New value: +[
+  "data",
+  "summary"
+]
  2. Changed3 schema fields changed
    • addedOutput schema / properties / data / items / properties / cancellation_requests
      Added value: +{
+  "items": {
+    "additionalProperties": {},
+    "properties": {
+      "id": {
+        "minLength": 1,
+        "type": "string"
+      },
+      "reason": {
+        "type": "string"
+      },
+      "status": {
+        "type": "string"
+      }
+    },
+    "required": [
+      "id",
+      "status",
+      "reason"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}
    • addedOutput schema / properties / data / items / properties / returns
      Added value: +{
+  "items": {
+    "additionalProperties": {},
+    "properties": {
+      "id": {
+        "minLength": 1,
+        "type": "string"
+      },
+      "reason": {
+        "type": "string"
+      },
+      "status": {
+        "type": "string"
+      }
+    },
+    "required": [
+      "id",
+      "status",
+      "reason"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}
    • addedOutput schema / properties / data / items / properties / warranty_claims
      Added value: +{
+  "items": {
+    "additionalProperties": {},
+    "properties": {
+      "description": {
+        "type": "string"
+      },
+      "id": {
+        "minLength": 1,
+        "type": "string"
+      },
+      "status": {
+        "type": "string"
+      }
+    },
+    "required": [
+      "id",
+      "status",
+      "description"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}
  3. Added

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive behavior. The description adds valuable semantic context by clarifying that plans and queued handoffs are never included, which is not directly inferable from the annotations. This helps the agent understand exactly what the result set contains.

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 concise sentences. The first states the core purpose, and the second adds a crucial exclusion criterion. There is no redundant wording and the most important information is front-loaded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a parameterless list tool with an output schema and comprehensive annotations, the description fully scopes the result set and clarifies a common point of confusion (what counts as an order). No additional information is needed to use the tool correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has zero parameters and is fully described (100% coverage). With no parameters, the description need not explain parameter syntax or purpose; the baseline of 4 applies.

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?

The description uses a specific verb ('list') and clearly identifies the resource ('merchant-confirmed orders for the buyer organization'). It also distinguishes the result set by explicitly excluding plans and queued handoffs, which helps separate it from other order-related tools like list_supplier_orders.

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?

The description provides clear context: it is scoped to the buyer organization and only includes merchant-confirmed orders. It also states what is not represented (plans/queued handoffs), giving implicit guidance on when to use this tool, though it does not explicitly name alternatives such as get_order or list_supplier_orders.

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

All SupplySlate toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources