Skip to main content
Glama

Update delivery

update_delivery
DestructiveIdempotent

Change instructions, contingency rules or the drop-off contact while in progress.

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": {
      "delivery_id": "<delivery_id>"
    },
    "name": "update_delivery"
  }
}

Input Schema

NameRequiredDescriptionDefault
metadataNo
window_endNo
contingencyNo
delivery_idYes
instructionsNo
dropoff_contactNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/5.0
Behavior2/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, but the description frames the operation as a benign field tweak and never explains what makes it destructive, whether omitted fields are cleared or preserved, or what happens when the delivery is not in progress. With annotations present the bar is lower, yet the description adds essentially no behavioral context for a write operation with a destructive flag.

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?

A single front-loaded sentence with no filler or redundancy, and the state constraint is placed at the end where it reads naturally. Its brevity is appropriate in form, though it leaves little room for the detail the operation needs.

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?

For a destructive, idempotent mutation with a six-parameter schema containing two nested objects, 0% schema description coverage, and no output schema, the definition is far too thin. An agent cannot tell from this text how partial updates behave, which nested enum values mean, or what a successful response confirms.

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 0%, so the description must carry the burden, and it names only three of six top-level parameters (instructions, contingency, dropoff_contact), leaving delivery_id, metadata, and window_end unaddressed. It also says nothing about the nested contingency enums (if_closed, if_no_answer) or max_wait_minutes, which are the parameters most likely to be misused.

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?

The description uses a specific verb ('Change') and enumerates the mutable facets: instructions, contingency rules, and drop-off contact, with a state qualifier ('while in progress'). The resource itself ('delivery') is only implied by the tool name, and no sibling such as cancel_delivery or confirm_delivery is contrasted, 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 Guidelines3/5

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

'While in progress' is a genuine precondition that tells the agent this is an in-flight modification, not a pre-booking edit. However, there is no guidance on when to prefer this over cancel_delivery, confirm_delivery, or create_return, and no mention of what to do if the delivery is past that state.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.