Skip to main content
Glama
Sign In
logistics-mcp

logistics-mcp

by Azzaraell
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

update_shipment_status

Update the status of a shipment to a specified value, optionally adding an operations note.

Instructions

Set the status of a shipment. Disabled unless the server runs with ALLOW_WRITES=1; in demo mode the change is kept in memory only. Use only when the user explicitly asks to change a status.

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": {
      "sp_number": "<sp_number>",
      "status": "<status>"
    },
    "name": "update_shipment_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
noteNoOptional ops note attached to the status event
statusYesNew status
sp_numberYesShipment number, e.g. SBY-1042

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A4.2/5.0
Behavior4/5

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

No annotations provided, so description carries full burden. Discloses that the tool is disabled without ALLOW_WRITES=1 and that demo mode changes are in-memory only. Good transparency for a mutation tool.

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 sentences with no waste. Front-loaded with main action. Every sentence adds value.

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?

Covers purpose, usage guidelines, and behavioral constraints adequately. No output schema, but description doesn't explain return values – minor gap for completeness.

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 baseline is 3. Description adds no additional meaning beyond the schema; parameters are already well-documented in the schema.

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?

Clearly states 'Set the status of a shipment' – specific verb and resource. Distinguishes from sibling tools like search_shipments, get_shipment (read-only), and track_shipment.

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?

Explicitly states 'Use only when the user explicitly asks to change a status.' Also mentions the ALLOW_WRITES=1 condition and demo mode behavior. Does not name alternative tools but context from siblings is clear.

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

Deploy Server

Other Tools