Skip to main content
Glama
gws8820

ShippingTracker

track_shipping

Monitor Korean shipment status by entering the company code and tracking invoice number for real-time delivery updates.

Instructions

Track Shipping with Company Code and Tracking Invoice

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
company_codeYes
tracking_invoiceYes

Implementation Reference

  • The main handler function for the 'track_shipping' tool. It uses the SweetTracker API to track a shipping invoice given a company code and tracking number. Registered via the @mcp.tool() decorator.
    @mcp.tool()
    def track_shipping(company_code: str, tracking_invoice: str):
        """
        Track Shipping with Company Code and Tracking Invoice
        """
        try:
            response = requests.post("https://info.sweettracker.co.kr/api/v1/trackingInfo", params = {"t_key": t_key, "t_code": company_code, "t_invoice": tracking_invoice})
            return response.json()
        except Exception as e:
            return {"error": str(e)}
Behavior2/5

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

With no annotations, the description carries full burden but only states what the tool does at a high level. It doesn't disclose behavioral traits such as whether it's read-only, requires authentication, has rate limits, returns real-time vs. cached data, or error handling. This is inadequate for a tool with no annotation coverage.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, concise sentence with no wasted words, but it's under-specified rather than efficiently informative. It's front-loaded but lacks depth, making it borderline between concise and 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?

Given no annotations, 0% schema coverage, no output schema, and a sibling tool, the description is incomplete. It doesn't explain return values, error cases, or how it relates to 'get_company_list'. For a 2-parameter tool with no structured support, more context is needed for effective use.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must compensate but only repeats parameter names ('Company Code and Tracking Invoice') without adding meaning. It doesn't explain what these parameters represent (e.g., company_code as carrier identifier, tracking_invoice as package ID), format, or examples, leaving semantics unclear.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Track Shipping with Company Code and Tracking Invoice' restates the tool name 'track_shipping' and lists parameters without specifying what tracking entails (e.g., retrieving status, location, or ETA). It distinguishes from sibling 'get_company_list' by implying action vs. list, but lacks a clear verb+resource definition like 'Retrieve shipping status for a package'.

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 guidance on when to use this tool versus alternatives is provided. The description implies usage for tracking shipments, but it doesn't specify prerequisites, exclusions, or compare to other tools (e.g., if 'get_company_list' is needed first). This leaves the agent without context for decision-making.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/gws8820/ShippingTracker'

If you have feedback or need assistance with the MCP directory API, please join our Discord server