Skip to main content
Glama

cancel_order

Cancel an order in ShipBob's fulfillment system by providing the order ID and optional reason, enabling order management adjustments.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
orderIdYesThe ID of the order to cancel
reasonNoReason for cancellation

Implementation Reference

  • The handler function for the 'cancel_order' tool. It destructures orderId and optional reason, prepares cancelData, calls shipbobClient.cancelOrder, and returns a formatted MCP response or error.
    handler: async ({ orderId, reason }) => {
      try {
        const cancelData = { reason };
        const result = await shipbobClient.cancelOrder(orderId, cancelData);
        return {
          content: [{ 
            type: "text", 
            text: `Order cancelled successfully: ${JSON.stringify(result, null, 2)}`
          }]
        };
      } catch (error) {
        return {
          content: [{ type: "text", text: `Error cancelling order: ${error.message}` }],
          isError: true
        };
      }
    }
  • Zod schema defining the input parameters for the cancel_order tool: orderId (required string) and reason (optional string).
    schema: {
      orderId: z.string().describe("The ID of the order to cancel"),
      reason: z.string().optional().describe("Reason for cancellation")
    },
  • src/server.js:51-51 (registration)
    Registers the orderTools array (which includes cancel_order) by calling registerTools, which in turn calls server.tool() for each tool.
    registerTools(orderTools);
  • ShipBobClient helper method that makes the POST request to the ShipBob API to cancel an order using the generic request method.
    async cancelOrder(id, cancelData) {
      return this.request('POST', `/orders/${id}/cancel`, cancelData);
    }
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