Skip to main content
Glama
hungryweb

CS-Cart MCP Server

by hungryweb

delete_product

Remove a product from your CS-Cart store by specifying its product ID to manage inventory and keep your catalog current.

Instructions

Delete a product from the store

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
product_idYesProduct ID to delete

Implementation Reference

  • The handler function that executes the delete_product tool. It sends a DELETE request to the CS-Cart API for the specified product_id and returns the response.
    async deleteProduct(args) {
      const result = await this.makeRequest('DELETE', `/products/${args.product_id}`);
      return { content: [{ type: 'text', text: JSON.stringify(result, null, 2) }] };
    }
  • The tool's schema definition, including name, description, and input schema requiring a product_id.
    {
      name: 'delete_product',
      description: 'Delete a product from the store',
      inputSchema: {
        type: 'object',
        properties: {
          product_id: {
            type: 'number',
            description: 'Product ID to delete',
          },
        },
        required: ['product_id'],
      },
    },
  • src/index.js:398-399 (registration)
    Registration in the CallToolRequestSchema switch statement that routes calls to delete_product to the deleteProduct handler method.
    case 'delete_product':
      return await this.deleteProduct(args);
Behavior2/5

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

No annotations are provided, so the description carries full burden. While 'Delete' implies a destructive mutation, the description doesn't disclose whether this operation is reversible, what permissions are required, whether it cascades to related data, or what happens on success/failure. For a destructive operation with zero annotation coverage, this is inadequate behavioral disclosure.

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 waste. It's appropriately sized for a simple delete operation and gets straight to the point without unnecessary elaboration.

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 destructive mutation tool with no annotations and no output schema, the description is insufficient. It doesn't explain what happens after deletion (e.g., confirmation message, error handling), whether there are side effects, or what the agent should expect. Given the complexity of a delete operation in a store context, more completeness 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 the single parameter 'product_id' clearly documented in the schema. The description doesn't add any parameter semantics beyond what the schema already provides (e.g., format examples, validation rules, or where to find product IDs). Baseline 3 is appropriate when 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 clearly states the action ('Delete') and target resource ('a product from the store'), providing specific verb+resource pairing. However, it doesn't explicitly distinguish this from sibling tools like 'update_product' or 'create_product' beyond the obvious difference in action verbs.

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. It doesn't mention prerequisites (e.g., product must exist), consequences of deletion, or when to choose deletion over other operations like updating product status. With multiple sibling tools available, this lack of context is a significant gap.

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