Skip to main content
Glama
baskcart

W3Ship MCP Server

by baskcart

get_order

Retrieve detailed order information by ID to track shipments and manage fulfillment processes.

Instructions

Retrieve detailed information about a specific Order (TMF622).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesThe generic Order ID

Implementation Reference

  • Tool handler for 'get_order' in the main server loop, which imports and calls the orderService.getOrder method.
    case 'get_order': {
        const { orderService } = await import('./orders/service.js');
        const id = args?.id as string;
        const order = await orderService.getOrder(id);
        if (!order) {
            return { content: [{ type: 'text', text: `Error: Order not found: ${id}` }], isError: true };
        }
        return { content: [{ type: 'text', text: JSON.stringify(order, null, 2) }] };
    }
  • The actual implementation of the getOrder logic that fetches the order data from the Redis/Valkey store.
    async getOrder(orderId: string): Promise<Order | null> {
        const data = await this.getClient().get(`order:${orderId}`);
        if (!data) return null;
        return JSON.parse(data);
    }
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It implies read-only access via 'Retrieve' but fails to disclose error handling (e.g., invalid ID), return value structure, caching behavior, or idempotency traits.

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?

Single sentence is efficiently structured with no redundant words. However, given the absence of annotations and output schema, the description may be overly terse rather than appropriately concise.

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?

Lacks output schema and annotations, yet the description fails to compensate by describing the return structure, field details, or error scenarios. The phrase 'detailed information' is vague and insufficient for an agent to predict the response shape.

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 'id' parameter is fully documented as 'The generic Order ID'). The description adds no additional parameter semantics, meeting the baseline for high-coverage schemas.

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?

Uses specific verb 'Retrieve' with resource 'Order' and references standard 'TMF622', clearly indicating a read operation. However, it does not explicitly distinguish from sibling 'create_order' or other 'get_' tools in the description text.

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?

Provides no guidance on when to use this tool versus alternatives like 'create_order' or 'get_cart', nor does it mention prerequisites such as needing a valid Order ID from a previous operation.

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/baskcart/w3ship-mcp-server'

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