Skip to main content
Glama

Kargom

Recent shipments

list_shipments
Read-only

The user’s most recent shipments with status, carrier, tracking number and recipient city.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

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

Input Schema

NameRequiredDescriptionDefault
limitNoHow many (default 10)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds the useful fact that results are recency-ordered and enumerates the returned fields, but says nothing about whether results are capped by the limit parameter by default or how empty results appear.

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 compact sentence with the resource front-loaded and no filler. It is a noun phrase rather than a verb-led statement, which slightly weakens action clarity but costs nothing in length.

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?

There is no output schema, so the description correctly takes on the job of naming the returned fields, and it does. For a one-optional-parameter read tool with full annotation coverage, the only real omission is any hint about result volume or ordering semantics beyond 'most recent'.

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%: the single optional limit parameter is documented with its default and 1-50 range. The description does not mention the limit or how it interacts with 'most recent', so it adds no meaning beyond the schema, which is the baseline case for one fully documented parameter.

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 the resource (the user's most recent shipments) and the payload fields returned (status, carrier, tracking number, recipient city), so an agent knows exactly what it gets. It is distinguishable from get_shipment only implicitly via the plural, 'most recent' framing; no explicit differentiation is stated.

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

Usage Guidelines2/5

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

There is no when-to-use or when-not guidance and no mention of the sibling get_shipment for single-record lookups. The word 'recent' hints at usage scope, but nothing tells an agent when to pick this over get_shipment or get_tracking_link.

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