Skip to main content
Glama

Kargom

Cargo tracking link

get_tracking_link
Read-only

The carrier’s own tracking page for a tracking number. No account needed.

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": {
      "carrier": "<carrier>",
      "tracking_number": "<tracking_number>"
    },
    "name": "get_tracking_link"
  }
}

Input Schema

NameRequiredDescriptionDefault
carrierYesCarrier
tracking_numberYesTracking number

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/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 usefully adds that the result points at the carrier's own page and requires no account, but does not clarify whether the link is validated, live, or what happens with an unrecognized tracking number.

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 short sentences, the core purpose front-loaded, with nothing redundant or padded.

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 two-parameter read-only link builder with no output schema, the definition covers purpose, auth expectation, and result nature adequately. A brief note that the return value is a URL string would make it fully complete.

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 coverage is 100% and the carrier parameter already carries the full enum of supported carriers, so the schema does the heavy lifting. The description adds no format or validity guidance for tracking_number beyond what the schema states.

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 resource: the carrier's own tracking page for a given tracking number. This implicitly distinguishes it from siblings like get_shipment (shipment data) by making clear the output is a link to an external carrier page, though it never names or contrasts an alternative tool.

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

Usage Guidelines3/5

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

Usage is only implied by the phrase 'for a tracking number'; there is no explicit statement of when to prefer this over get_shipment or other shipment lookups, nor any prerequisites beyond 'no account needed'.

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