Skip to main content
Glama

get_shipment

Retrieve shipment details from the ShipBob fulfillment API using a specific shipment ID to track order status and fulfillment information.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
shipmentIdYesThe ID of the shipment to retrieve

Implementation Reference

  • The handler function that implements the core logic of the 'get_shipment' tool. It fetches the shipment data via the ShipBob API client and returns it as formatted JSON, handling errors appropriately.
    handler: async ({ shipmentId }) => {
      try {
        const shipment = await shipbobClient.getShipment(shipmentId);
        return {
          content: [{ 
            type: "text", 
            text: JSON.stringify(shipment, null, 2)
          }]
        };
      } catch (error) {
        return {
          content: [{ type: "text", text: `Error retrieving shipment: ${error.message}` }],
          isError: true
        };
      }
    }
  • The Zod input schema for the 'get_shipment' tool, defining the required shipmentId parameter.
    schema: {
      shipmentId: z.string().describe("The ID of the shipment to retrieve")
    },
  • src/server.js:23-32 (registration)
    The registerTools function used to register all tools from arrays like fulfillmentTools, including 'get_shipment', by calling server.tool() for each.
    const registerTools = (toolsArray) => {
      toolsArray.forEach(tool => {
        server.tool(
          tool.name,
          tool.schema,
          tool.handler,
          { description: tool.description }
        );
      });
    };
  • src/server.js:53-53 (registration)
    Specific call to register the fulfillmentTools array, which includes the 'get_shipment' tool.
    registerTools(fulfillmentTools);
  • The ShipBobClient.getShipment method called by the tool handler to perform the actual API request for shipment details.
    async getShipment(id) {
      return this.request('GET', `/shipments/${id}`);
    }
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/shipbob-mcp-server'

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