Skip to main content
Glama
hungryweb

CS-Cart MCP Server

by hungryweb

update_order_status

Change order status in CS-Cart stores to manage fulfillment workflows, with options to notify customers about updates.

Instructions

Update order status

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
order_idYesOrder ID
statusYesNew order status (O=Open, P=Processed, C=Complete, F=Failed, D=Declined, B=Backordered, I=Incomplete)
notify_userNoWhether to notify the user about status change

Implementation Reference

  • The handler function that executes the tool logic: destructures the arguments to separate order_id and other data, makes a PUT request to the CS-Cart orders API endpoint, and returns the formatted JSON response.
    async updateOrderStatus(args) {
      const { order_id, ...orderData } = args;
      const result = await this.makeRequest('PUT', `/orders/${order_id}`, orderData);
      return { content: [{ type: 'text', text: JSON.stringify(result, null, 2) }] };
    }
  • Input schema for the tool, defining required order_id and status (with enum), and optional notify_user boolean.
    inputSchema: {
      type: 'object',
      properties: {
        order_id: {
          type: 'number',
          description: 'Order ID',
        },
        status: {
          type: 'string',
          description: 'New order status (O=Open, P=Processed, C=Complete, F=Failed, D=Declined, B=Backordered, I=Incomplete)',
          enum: ['O', 'P', 'C', 'F', 'D', 'B', 'I'],
        },
        notify_user: {
          type: 'boolean',
          description: 'Whether to notify the user about status change',
          default: true,
        },
      },
      required: ['order_id', 'status'],
    },
  • src/index.js:301-324 (registration)
    Tool registration in the ListTools response, including name, description, and full input schema.
    {
      name: 'update_order_status',
      description: 'Update order status',
      inputSchema: {
        type: 'object',
        properties: {
          order_id: {
            type: 'number',
            description: 'Order ID',
          },
          status: {
            type: 'string',
            description: 'New order status (O=Open, P=Processed, C=Complete, F=Failed, D=Declined, B=Backordered, I=Incomplete)',
            enum: ['O', 'P', 'C', 'F', 'D', 'B', 'I'],
          },
          notify_user: {
            type: 'boolean',
            description: 'Whether to notify the user about status change',
            default: true,
          },
        },
        required: ['order_id', 'status'],
      },
    },
  • src/index.js:408-409 (registration)
    Dispatch/registration in the CallToolRequest switch statement that calls the handler method.
    case 'update_order_status':
      return await this.updateOrderStatus(args);
Behavior1/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. 'Update order status' implies a mutation operation but reveals nothing about permissions required, whether changes are reversible, side effects (like notifications), rate limits, or what happens on success/failure. For a mutation tool with zero annotation coverage, this is a critical gap that leaves the agent guessing about important behavioral traits.

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

Conciseness2/5

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

While technically concise with just three words, this is under-specification rather than effective brevity. The description fails to provide essential context that would help an agent use the tool correctly. Every sentence should earn its place, but here the single phrase doesn't provide enough value to justify its existence as a helpful 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?

This is a mutation tool with no annotations, no output schema, and sibling tools that could be confused with it. The description is completely inadequate - it doesn't explain what the tool does beyond the name, provides no behavioral context, offers no usage guidance, and leaves critical questions unanswered about permissions, side effects, and error conditions.

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%, so the schema already fully documents all three parameters (order_id, status with enum values, notify_user with default). The description adds no additional meaning beyond what's in the schema - it doesn't explain parameter interactions, constraints, or usage nuances. With complete schema coverage, the baseline score of 3 is appropriate.

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

Purpose2/5

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

The description 'Update order status' is essentially a tautology that restates the tool name. While it includes a verb ('Update') and resource ('order status'), it lacks specificity about what this operation entails or how it differs from other order-related tools like 'get_order' or 'update_product'. It doesn't distinguish itself from siblings beyond the obvious name difference.

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?

The description provides no guidance on when to use this tool versus alternatives. There are sibling tools like 'get_order' and 'update_product' that might be relevant in similar contexts, but the description offers no explicit or implicit advice on when this tool is appropriate, what prerequisites exist, or when to choose other tools instead.

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/hungryweb/cscart-mcp-server'

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