Skip to main content
Glama
hungryweb

CS-Cart MCP Server

by hungryweb

update_product_stock

Modify inventory levels for products in CS-Cart stores by specifying product ID and new quantity to maintain accurate stock counts.

Instructions

Update product stock quantity

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
product_idYesProduct ID
amountYesNew stock quantity

Implementation Reference

  • The handler function for 'update_product_stock' that updates the stock quantity of a product by making a PUT request to the CS-Cart API with the new amount.
    async updateProductStock(args) {
      const productData = { amount: args.amount };
      const result = await this.makeRequest('PUT', `/products/${args.product_id}`, productData);
      return { content: [{ type: 'text', text: JSON.stringify(result, null, 2) }] };
    }
  • Defines the tool schema including name, description, and input schema for validating arguments (product_id and amount).
    {
      name: 'update_product_stock',
      description: 'Update product stock quantity',
      inputSchema: {
        type: 'object',
        properties: {
          product_id: {
            type: 'number',
            description: 'Product ID',
          },
          amount: {
            type: 'number',
            description: 'New stock quantity',
          },
        },
        required: ['product_id', 'amount'],
      },
    },
  • src/index.js:400-401 (registration)
    Registers the tool handler in the CallToolRequestSchema switch statement, dispatching calls to updateProductStock.
    case 'update_product_stock':
      return await this.updateProductStock(args);
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. 'Update product stock quantity' implies a mutation operation but doesn't specify whether this requires special permissions, if it's idempotent, what happens with invalid amounts (e.g., negative values), or how it affects related data (e.g., inventory logs). For a mutation tool with zero annotation coverage, this is insufficient.

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

Conciseness5/5

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

The description is a single, efficient sentence with zero wasted words. It's front-loaded with the core purpose and appropriately sized for a simple update operation. Every word earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a mutation tool with no annotations and no output schema, the description is incomplete. It doesn't explain what the tool returns (e.g., success confirmation, updated product object, error details) or address potential side effects. Given the complexity of stock updates (which could trigger inventory events), more context is needed.

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%, with both parameters ('product_id' and 'amount') clearly documented in the schema. The description adds no additional parameter semantics beyond what the schema provides (e.g., no clarification on 'amount' units or valid ranges). Baseline 3 is appropriate when the schema does the heavy lifting.

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

Purpose4/5

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

The description 'Update product stock quantity' clearly states the action (update) and the target resource (product stock quantity). It distinguishes from siblings like 'create_product' or 'update_product' by focusing specifically on stock quantity rather than general product attributes or creation. However, it doesn't explicitly differentiate from 'update_product' which might also handle stock updates.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/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 like 'update_product' (which might handle stock) or 'get_product' (for checking current stock). There's no mention of prerequisites, constraints, or typical usage scenarios. The agent must infer usage from the tool name alone.

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