Skip to main content
Glama
gws8820

ShippingTracker

get_company_list

Retrieve a list of available shipping companies for tracking Korean parcel deliveries through the ShippingTracker MCP server.

Instructions

Get Company List

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function for the 'get_company_list' tool. It is decorated with @mcp.tool() for registration and fetches the list of shipping companies from the SweetTracker API using the API key from the SWEETTRACKER_API_KEY environment variable.
    @mcp.tool()
    def get_company_list():
        """
        Get Company List
        """
        try:
            response = requests.get("https://info.sweettracker.co.kr/api/v1/companylist", params = {"t_key": t_key})
            return response.json()
        except Exception as e:
            return {"error": str(e)}
  • The @mcp.tool() decorator registers the get_company_list function as an MCP tool.
    @mcp.tool()
Behavior1/5

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

No annotations are provided, so the description must fully disclose behavioral traits. It fails to mention any details such as whether this is a read-only operation, if it requires authentication, potential rate limits, or what the output format might be. This leaves the agent with no behavioral context.

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

Conciseness2/5

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

While the description is brief, it is under-specified rather than concise. 'Get Company List' is too minimal to be helpful, failing to provide necessary context or structure. It does not earn its place as a useful description.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the lack of annotations and output schema, the description is incomplete. It does not explain what 'Company List' includes, how results are returned, or any operational constraints. For a tool with no structured support, this description is inadequate.

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?

The tool has 0 parameters, and schema description coverage is 100%, so there is no need for parameter details in the description. The baseline for this scenario is 4, as the absence of parameters is adequately handled by the schema, and the description does not need to compensate.

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 'Get Company List' restates the tool name with minimal elaboration, making it a tautology. It specifies the verb 'Get' and resource 'Company List' but lacks any detail about what this entails or how it differs from the sibling tool 'track_shipping', leaving the purpose vague.

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

Usage Guidelines1/5

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

No guidance is provided on when to use this tool versus the sibling 'track_shipping' or any other context. The description offers no explicit or implied usage scenarios, prerequisites, or alternatives, making it completely unhelpful 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