Skip to main content
Glama
modellers

ConsignCloud MCP Server

by modellers

list_batches

Retrieve and filter batches of items in ConsignCloud by status, account, or using pagination to manage consignment operations.

Instructions

List batches of items

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoNumber of results (default: 1000)
cursorNo
statusNo
accountNoFilter by account ID

Implementation Reference

  • The MCP tool handler for 'list_batches'. It merges input arguments with a default limit of 1000, calls the client's listBatches method, stringifies the result as JSON, and returns it in the MCP response format.
    case 'list_batches':
      const batchesParams = { limit: 1000, ...(args as any) };
      return { content: [{ type: 'text', text: JSON.stringify(await client.listBatches(batchesParams), null, 2) }] };
  • src/server.ts:290-302 (registration)
    Registration of the 'list_batches' tool in the tools array returned by createTools(), including its name, description, and input schema for MCP tool listing.
    {
      name: 'list_batches',
      description: 'List batches of items',
      inputSchema: {
        type: 'object',
        properties: {
          limit: { type: 'number', description: 'Number of results (default: 1000)' },
          cursor: { type: 'string' },
          status: { type: 'string', enum: ['draft', 'submitted'] },
          account: { type: 'string', description: 'Filter by account ID' },
        },
      },
    },
  • Input schema definition for the 'list_batches' tool, defining optional parameters like limit, cursor, status, and account.
    inputSchema: {
      type: 'object',
      properties: {
        limit: { type: 'number', description: 'Number of results (default: 1000)' },
        cursor: { type: 'string' },
        status: { type: 'string', enum: ['draft', 'submitted'] },
        account: { type: 'string', description: 'Filter by account ID' },
      },
    },
  • Client-side helper method listBatches that performs an HTTP GET request to '/batches' endpoint with provided parameters and returns the paginated response.
    async listBatches(params?: Record<string, any>): Promise<PaginatedResponse<Batch>> {
      const response = await this.client.get('/batches', { params });
      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 full burden for behavioral disclosure. It only states the action ('List') without details on permissions, rate limits, pagination behavior (implied by 'cursor' parameter but not explained), or response format. This is inadequate for a tool with multiple parameters and no output schema.

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 no wasted words. It is appropriately sized for a basic tool, though this conciseness comes at the cost of detail.

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?

Given the tool has 4 parameters, no annotations, no output schema, and 50% schema coverage, the description is incomplete. It lacks essential context such as behavioral traits, parameter explanations for 'cursor' and 'status', and differentiation from siblings, making it insufficient for effective agent use.

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 50% (2 of 4 parameters have descriptions). The description adds no additional parameter semantics beyond the schema, failing to compensate for the undocumented 'cursor' and 'status' parameters. Baseline is 3 since the schema provides some coverage, but the description does not enhance it.

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

Purpose3/5

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

The description 'List batches of items' states a verb ('List') and resource ('batches of items'), providing a basic purpose. However, it lacks specificity about what 'batches' entail (e.g., processing batches, inventory batches) and does not differentiate from sibling tools like 'list_accounts' or 'list_items', leaving ambiguity about scope.

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?

No guidance is provided on when to use this tool versus alternatives. It does not mention prerequisites, context for filtering (e.g., vs. 'list_items'), or exclusions, leaving the agent to infer usage based on 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/modellers/mcp-consigncloud'

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