Skip to main content
Glama
Sign In

Pizza Developer

by com.pizzadeveloper
OverviewDiscussionsAdmin

Update delivery

update_delivery
Destructive

Edit a delivery's own record (name, rationale, summary, ship date) and add or remove its batches. Only supplied fields change; pass an empty string to clear a text field. addBatchIds puts ready batches that no delivery carries into this one, and removeBatchIds takes batches out of it; every other batch stays. Take a batch out of its current delivery before adding it to another. shippedAt corrects when it shipped (ISO date or date-time, not in the future). The name is a free-form label and must stay non-empty and unique within its project. Returns the delivery's resulting batches. At a workflow run's Delivery stage, adding every ready Batch of the run to one existing Delivery completes the stage instead of create_delivery. In a run of a workflow that starts at Delivery, adding any ready Batch no delivery carries to an existing Delivery completes the stage. Inside a workflow run, rules are checked by TypeSafe, a separate provider, which receives the record, the text of each Rule, and the project context a Rule refers to.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "id": "<id>"
    },
    "name": "update_delivery"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesId of the Delivery.
nameNoNew Delivery name, a free-form label.
metricsNoOptional client measurements, stored on the workflow step this call completes.
summaryNoWhat shipped; an empty string clears it.
rationaleNoWhy the Delivery exists; an empty string clears it.
shippedAtNoShip date, as an ISO date or date-time.
addBatchIdsNoReady Batches to add.
removeBatchIdsNoBatches to take out.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / name
      Added value: +{
+  "description": "New Delivery name, a free-form label.",
+  "minLength": 1,
+  "type": "string"
+}
    • removedInput schema / properties / version
      Removed value: -{
-  "description": "Version label, such as 2.4.0.",
-  "minLength": 1,
-  "type": "string"
-}
  2. Changed4 schema fields changed
    • addedInput schema / properties / addBatchIds
      Added value: +{
+  "description": "Ready Batches to add.",
+  "items": {
+    "minLength": 1,
+    "type": "string"
+  },
+  "type": "array"
+}
    • removedInput schema / properties / batchIds
      Removed value: -{
-  "description": "Full replacement set of Batches.",
-  "items": {
-    "minLength": 1,
-    "type": "string"
-  },
-  "type": "array"
-}
    • addedInput schema / properties / metrics
      Added value: +{
+  "description": "Optional client measurements, stored on the workflow step this call completes.",
+  "properties": {
+    "durationMs": {
+      "maximum": 9007199254740991,
+      "minimum": 0,
+      "type": "integer"
+    },
+    "inputTokens": {
+      "maximum": 9007199254740991,
+      "minimum": 0,
+      "type": "integer"
+    },
+    "model": {
+      "maxLength": 120,
+      "type": "string"
+    },
+    "outputTokens": {
+      "maximum": 9007199254740991,
+      "minimum": 0,
+      "type": "integer"
+    },
+    "retryCount": {
+      "maximum": 9007199254740991,
+      "minimum": 0,
+      "type": "integer"
+    },
+    "toolCallCount": {
+      "maximum": 9007199254740991,
+      "minimum": 0,
+      "type": "integer"
+    }
+  },
+  "type": "object"
+}
    • addedInput schema / properties / removeBatchIds
      Added value: +{
+  "description": "Batches to take out.",
+  "items": {
+    "minLength": 1,
+    "type": "string"
+  },
+  "type": "array"
+}
  3. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Goes well beyond annotations: partial-update semantics ("Only supplied fields change"), empty-string clearing, name uniqueness/non-empty constraint, shippedAt must not be in the future, and the return value (resulting batches). It also discloses that rule checks run through TypeSafe, a separate provider — a non-obvious side effect of the mutation that annotations cannot convey.

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?

Front-loaded with the core edit operation and update semantics before the more situational workflow-stage rules. It is dense but nearly every sentence carries distinct information; the TypeSafe and stage-completion sentences are long yet load-bearing for correct invocation.

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?

With no output schema, the description still states what comes back ("the delivery's resulting batches"). For an 8-parameter destructive mutation it covers partial-update behavior, clearing semantics, constraints, reassignment ordering, and workflow-stage side effects — everything needed to call it 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?

Schema coverage is 100%, so baseline is 3; the description earns above that by clarifying addBatchIds/removeBatchIds scope, shippedAt format and future-date restriction, and name constraints. It never mentions the `metrics` object, leaving one of eight parameters to the schema alone.

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?

Opens with a specific verb+resource: "Edit a delivery's own record" and enumerates the editable fields (name, rationale, summary, ship date) plus batch membership. This is clearly distinguished from sibling mutations like create_delivery, delete_delivery, and update_delivery_presentation.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly states when to use addBatchIds (ready batches no delivery carries) and the precondition for reassigning a batch ("Take a batch out of its current delivery before adding it to another"). It also names the concrete alternative to create_delivery: adding all ready Batch of a run to an existing Delivery completes the stage instead.

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

All Pizza Developer 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