Skip to main content
Glama
modellers

ConsignCloud MCP Server

by modellers

list_sales

Retrieve sales data from ConsignCloud with filters for status, customer, location, date range, and pagination to manage consignment business operations.

Instructions

List sales with optional filters

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoNumber of results (default: 1000)
cursorNoPagination cursor
statusNoFilter by status (completed, voided, returned)
customerNoFilter by customer account ID
locationNoFilter by location ID
created_gteNoFilter sales created after this date (ISO 8601)
created_lteNoFilter sales created before this date (ISO 8601)

Implementation Reference

  • MCP tool handler for 'list_sales': constructs params with default limit 1000, calls client.listSales(), and returns JSON stringified response.
    case 'list_sales':
      const salesParams = { limit: 1000, ...(args as any) };
      return { content: [{ type: 'text', text: JSON.stringify(await client.listSales(salesParams), null, 2) }] };
  • Input schema definition for the 'list_sales' tool, including properties for pagination, filtering by status, customer, location, and date ranges.
    {
      name: 'list_sales',
      description: 'List sales with optional filters',
      inputSchema: {
        type: 'object',
        properties: {
          limit: { type: 'number', description: 'Number of results (default: 1000)' },
          cursor: { type: 'string', description: 'Pagination cursor' },
          status: { type: 'string', description: 'Filter by status (completed, voided, returned)' },
          customer: { type: 'string', description: 'Filter by customer account ID' },
          location: { type: 'string', description: 'Filter by location ID' },
          created_gte: { type: 'string', description: 'Filter sales created after this date (ISO 8601)' },
          created_lte: { type: 'string', description: 'Filter sales created before this date (ISO 8601)' },
        },
      },
    },
  • src/server.ts:418-420 (registration)
    Registration of all tools list handler, which returns the array including 'list_sales' from createTools().
    server.setRequestHandler(ListToolsRequestSchema, async () => ({
      tools,
    }));
  • Client method listSales that proxies HTTP GET /sales with params, converts response using convertSaleResponse, returns PaginatedResponse<Sale>.
    async listSales(params?: Record<string, any>): Promise<PaginatedResponse<Sale>> {
      const response = await this.client.get('/sales', { params });
      return {
        data: response.data.data.map((sale: any) => this.convertSaleResponse(sale)),
        next_cursor: response.data.next_cursor,
      };
    }
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. It mentions 'optional filters' but doesn't specify whether this is a read-only operation, if it requires authentication, what the return format looks like, or any rate limits. For a list tool with 7 parameters and no annotation coverage, this is inadequate.

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 and front-loaded, stating the core purpose immediately without unnecessary elaboration.

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

Completeness3/5

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

Given the tool's moderate complexity (7 parameters, no output schema, no annotations), the description is minimally adequate but incomplete. It covers the basic purpose but lacks behavioral context, usage guidelines, and output information that would be helpful for an AI agent.

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 fully documents all 7 parameters. The description adds no additional parameter information beyond implying filtering exists. This meets the baseline of 3 where the schema does the heavy lifting, but the description doesn't compensate or add value.

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 'List sales with optional filters' clearly states the verb ('list') and resource ('sales'), and implies scope ('with optional filters'). However, it doesn't differentiate from sibling tools like 'get_sale' (singular) or 'get_sales_trends' (analytics-focused), missing specific sibling distinction that would warrant a 5.

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_sale' for single sales or 'get_sales_trends' for analytics. It lacks explicit when/when-not instructions or named alternatives, offering only implied usage through the word 'list'.

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/modellers/mcp-consigncloud'

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