Skip to main content
Glama
Sign In
Local MCP

Local MCP

by colibird-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

amazon_track_shipment

Track an Amazon order shipment to retrieve its status, carrier, tracking ID, and expected delivery date.

Instructions

(Beta) Tracks a shipment of one of the person's own Amazon orders: status, carrier, tracking id, expected d...

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": "amazon_track_shipment"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.0.446

TDQS

B3.2/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It discloses that the lookup is scoped to the person's own orders, is a retrieval-style operation returning shipment attributes, and is marked beta. It does not mention whether an authenticated Amazon connection is required, whether tracking data may be stale, or how a missing shipment is reported.

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 beta marker front-loaded and the action immediately following. Nothing is wasted, though the truncated ending leaves the enumeration visibly incomplete.

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?

A zero-parameter tool with no annotations and no output schema, so the description must explain the return contents and prerequisites itself. It starts to list returned fields but cuts off, and never states connection or auth requirements, leaving the definition materially incomplete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

There are zero input parameters, so there is nothing for the description to document and the baseline of 4 applies. The one semantic constraint it does convey is that the order must belong to the person making the call.

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?

States a specific verb and resource: tracks a shipment of the person's own Amazon order, and begins enumerating what is returned (status, carrier, tracking id, expected date). It is clearly separable from amazon_get_order, although the description is truncated ('expected d...'), leaving the field list unfinished.

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?

No explicit when-to-use guidance or exclusions. It implies the tool applies to shipments on the person's own orders, but never says when to prefer amazon_get_order, nor what to do when no shipment exists for an order.

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