Skip to main content
Glama
mattcoatsworth

ShipStation API MCP Server

get_order

Retrieve specific order details from ShipStation using the order ID to access shipping information, customer data, and fulfillment status.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
orderIdYesOrder ID to retrieve

Implementation Reference

  • The handler function for the 'get_order' MCP tool. It takes an orderId, fetches the order using shipStationClient.getOrder, stringifies it to JSON, and returns it in the expected MCP format. Handles errors by returning an error message.
    handler: async ({ orderId }) => {
      try {
        const order = await shipStationClient.getOrder(orderId);
        return {
          content: [{ type: "text", text: JSON.stringify(order, null, 2) }]
        };
      } catch (error) {
        return {
          content: [{ type: "text", text: error.message }],
          isError: true
        };
      }
    }
  • Zod input schema for the 'get_order' tool, validating that orderId is a required number.
    schema: {
      orderId: z.number().describe("Order ID to retrieve")
    },
  • src/server.js:184-191 (registration)
    The registration logic in the MCP server that iterates over all tools (including 'get_order' from orderTools) and calls server.tool to register each one with its name, schema, handler, and description.
    ].forEach(tool => {
      server.tool(
        tool.name,
        tool.schema,
        tool.handler,
        { description: tool.description }
      );
    });
  • Helper method in ShipStationClient that performs the actual API GET request to retrieve a specific order by ID from ShipStation's /orders/{orderId} endpoint.
    async getOrder(orderId) {
      return this.request('GET', `/orders/${orderId}`);
    }
Behavior1/5

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

Tool has no description.

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

Conciseness1/5

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

Tool has no 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?

Tool has no description.

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

Parameters1/5

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

Tool has no description.

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

Purpose1/5

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

Tool has no description.

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?

Tool has no description.

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/mattcoatsworth/shipstation-mcp-server'

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