Skip to main content
Glama

Kargom

Shipment details

get_shipment
Read-only

Status, tracking link and label link of one shipment (by shipment_id, Kargom reference, or the approval_id from prepare_shipment).

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

Input Schema

NameRequiredDescriptionDefault
shipment_idYesshipment_id, reference or approval_id

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, destructiveHint false, and openWorldHint false, so safety and scope are covered by structured data. The description adds value by disclosing the returned fields (status, tracking link, label link), which matters because there is no output schema. It says nothing about failure modes such as an unknown reference or an unapproved shipment.

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?

One sentence, front-loaded with the returned data, then the identifier options in parentheses. Every clause carries information and there is no filler.

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?

For a single-parameter read tool with full annotation coverage and full schema coverage, the description supplies the missing piece — what comes back. The only residual gap is error behavior for invalid or unknown identifiers, which is minor at this complexity.

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% and the single parameter's schema text ('shipment_id, reference or approval_id') already covers the polymorphic identifier. The description restates the same fact rather than adding format, length, or validation nuance, so the baseline of 3 applies.

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 names a specific resource (one shipment) and enumerates exactly what it returns: status, tracking link, and label link. The phrase 'one shipment' implicitly separates it from list_shipments, but it never names a sibling explicitly, so differentiation is inferred rather than stated.

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?

It gives concrete usage context by naming the three acceptable identifiers, including 'the approval_id from prepare_shipment', which tells an agent this tool is the natural follow-up to that workflow. It stops short of stating when to prefer get_tracking_link instead, so there are no explicit exclusions.

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.

Resources