Skip to main content
Glama
hungryweb

CS-Cart MCP Server

by hungryweb

get_order

Retrieve detailed order information from CS-Cart stores by providing an order ID to view customer details, items, and status.

Instructions

Get detailed information about a specific order

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
order_idYesOrder ID

Implementation Reference

  • The main handler function that executes the get_order tool by making a GET request to the CS-Cart API endpoint for the specific order ID.
    async getOrder(args) {
      const result = await this.makeRequest('GET', `/orders/${args.order_id}`);
      return { content: [{ type: 'text', text: JSON.stringify(result, null, 2) }] };
    }
  • The input schema and metadata for the get_order tool, defining it requires an order_id parameter.
    {
      name: 'get_order',
      description: 'Get detailed information about a specific order',
      inputSchema: {
        type: 'object',
        properties: {
          order_id: {
            type: 'number',
            description: 'Order ID',
          },
        },
        required: ['order_id'],
      },
    },
  • src/index.js:406-407 (registration)
    Registration in the CallToolRequestHandler switch statement that dispatches to the getOrder handler.
    case 'get_order':
      return await this.getOrder(args);
  • src/index.js:288-300 (registration)
    Tool registration in the ListToolsRequestHandler response, listing the get_order tool with its schema.
      name: 'get_order',
      description: 'Get detailed information about a specific order',
      inputSchema: {
        type: 'object',
        properties: {
          order_id: {
            type: 'number',
            description: 'Order ID',
          },
        },
        required: ['order_id'],
      },
    },
  • Shared helper method used by getOrder to make authenticated API requests to CS-Cart.
    async makeRequest(method, endpoint, data = null) {
      const config = {
        method,
        url: `${process.env.CSCART_API_URL}${endpoint}`,
        headers: {
          'Content-Type': 'application/json',
          'Authorization': `Basic ${Buffer.from(`${process.env.CSCART_API_EMAIL}:${process.env.CSCART_API_KEY}`).toString('base64')}`,
        },
      };
    
      if (data) {
        config.data = data;
      }
    
      const response = await axios(config);
      return response.data;
    }
Behavior2/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. It states the tool retrieves 'detailed information,' implying a read-only operation, but doesn't specify what details are included, whether authentication is required, potential error conditions, or response format. This leaves significant gaps for a tool with no annotation coverage.

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 that directly states the tool's purpose without unnecessary words. It is front-loaded and wastes no space, making it easy for an agent to parse quickly.

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 tool with no annotations and no output schema, the description is insufficient. It doesn't explain what 'detailed information' includes, how errors are handled, or any behavioral traits. Given the complexity of order data and the lack of structured fields, more context is needed to ensure the agent can use the tool effectively.

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?

The input schema has 100% description coverage, with the single parameter 'order_id' documented as 'Order ID.' The description adds no additional meaning beyond this, such as format examples or constraints. Given the high schema coverage, a baseline score of 3 is appropriate, as the schema already provides adequate parameter information.

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 tool's purpose with a specific verb ('Get') and resource ('detailed information about a specific order'), making it immediately understandable. However, it doesn't explicitly distinguish this from sibling tools like 'get_orders' (plural) or 'update_order_status', which could cause confusion about when to use each one.

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 'get_orders' (for listing multiple orders) or 'update_order_status' (for modifying orders). It lacks any context about prerequisites, such as needing an existing order ID, or exclusions, leaving the agent to 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