Skip to main content
Glama
Sign In
logistics-mcp

logistics-mcp

by Azzaraell
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

get_shipment

Retrieve complete shipment details including items, extra charges, total amount, and full status history for any shipment number.

Instructions

Full detail for one shipment: items, extra charges, total amount, and the complete status history. Use after search_shipments when the summary is not enough.

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>"
    },
    "name": "get_shipment"
  }
}

Input Schema

NameRequiredDescriptionDefault
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 bears full burden. It describes the return content (items, charges, amount, status history), implying read-only. Adds behavioral context beyond the input schema by detailing the output, though doesn't mention errors or permissions.

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: first states purpose and output, second gives usage guidance. Front-loads key information with zero wasted words.

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?

Single parameter, no output schema. Description adequately explains what the tool returns and when to use it. Lacks error handling details but is sufficient for the tool's simplicity.

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% for the sole parameter sp_number, which already includes type, pattern, and example. The tool description does not add new parameter semantics; baseline score of 3 is appropriate.

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?

Description clearly states 'Full detail for one shipment' and lists specific data items (items, extra charges, total amount, complete status history). It distinguishes from sibling 'search_shipments' by noting it provides more detail when summary is insufficient.

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?

Provides explicit context: 'Use after search_shipments when the summary is not enough.' This tells the agent when to call this tool vs. the sibling. No exclusions mentioned, but the guidance 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