Skip to main content
Glama

adjust_inventory

Update product inventory levels in ShipBob fulfillment centers by adding or reducing stock quantities with specified reasons.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
productIdYesThe ID of the product to adjust
fulfillmentCenterIdYesThe ID of the fulfillment center
quantityYesQuantity to adjust (positive for addition, negative for reduction)
reasonYesReason for the adjustment

Implementation Reference

  • Executes the adjust_inventory tool logic: constructs adjustment data and calls shipbobClient.adjustInventory API method, handles response or error.
    handler: async ({ productId, fulfillmentCenterId, quantity, reason }) => {
      try {
        const adjustmentData = {
          productId,
          fulfillmentCenterId,
          quantity,
          reason
        };
        const result = await shipbobClient.adjustInventory(adjustmentData);
        return {
          content: [{ 
            type: "text", 
            text: `Inventory adjusted successfully: ${JSON.stringify(result, null, 2)}`
          }]
        };
      } catch (error) {
        return {
          content: [{ type: "text", text: `Error adjusting inventory: ${error.message}` }],
          isError: true
        };
      }
  • Zod input schema for adjust_inventory tool parameters.
    schema: {
      productId: z.string().describe("The ID of the product to adjust"),
      fulfillmentCenterId: z.string().describe("The ID of the fulfillment center"),
      quantity: z.number().describe("Quantity to adjust (positive for addition, negative for reduction)"),
      reason: z.string().describe("Reason for the adjustment")
  • src/server.js:52-52 (registration)
    Registers the inventoryTools array (containing adjust_inventory) with the MCP server via the registerTools helper function.
    registerTools(inventoryTools);
  • ShipBobClient helper method that sends POST request to ShipBob API endpoint for inventory adjustment.
    async adjustInventory(adjustmentData) {
      return this.request('POST', '/inventory/adjustments', adjustmentData);
    }
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