Skip to main content
Glama

SupplySlate

by com.supplyslate
OverviewDiscussionsAdmin

update_supplier_order

Acknowledge or update fulfillment on a merchant-confirmed supplier order, optionally recording a shipment. State transitions and order-item quantities are validated and audited.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
noteNo
statusYes
order_idYes
shipmentNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
orderYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedOutput schema / properties / order / 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 / order / 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 / order / 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"
+}
  2. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already indicate this is a non-read-only, non-idempotent operation, and the description adds valuable behavioral context: 'State transitions and order-item quantities are validated and audited.' This tells the agent that invalid status changes will be rejected and that changes are logged. It does not disclose failure modes or permission requirements, but with annotations covering the basic safety profile, this is acceptable.

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?

The description is two concise sentences with no filler. The first sentence states the core action and optional shipment behavior; the second adds validation/audit context. It is well-structured and front-loaded.

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

Completeness2/5

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

Despite the tool's complexity (nested shipment object, status enum, 4 parameters), the description does not specify allowed state transitions, when the shipment object should be provided, or how statuses relate to fulfillment stages. The presence of an output schema covers return values, but the description leaves critical usage context unanswered for an agent invoking this tool.

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

Parameters2/5

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

Schema description coverage is 0%, and the description only indirectly references parameters via 'optionally recording a shipment.' It does not explain the meaning of status values, the order_id format, or the contents of the shipment object, leaving the agent to infer from property names and enums alone. Since schema coverage is zero, the description fails to compensate, making this dimension weak.

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 clearly states the tool's function: 'Acknowledge or update fulfillment on a merchant-confirmed supplier order, optionally recording a shipment.' It specifies the verb (update), resource (supplier order), and key sub-behavior (shipment recording), which distinguishes it from sibling tools like update_supplier_order_issue or request_order_cancellation.

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?

The description implies the order must be 'merchant-confirmed' but does not explicitly state when to use this tool versus alternatives such as request_order_cancellation or update_supplier_order_issue. It provides context (fulfillment updates) but no exclusions or alternative tool guidance, so usage guidance is only partially explicit.

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