Skip to main content
Glama
modellers

ConsignCloud MCP Server

by modellers

void_sale

Cancel or reverse a completed sale transaction in ConsignCloud by providing the sale ID to correct errors or process returns.

Instructions

Void a sale

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesSale ID

Implementation Reference

  • MCP server handler for the 'void_sale' tool. Extracts the sale ID from input arguments and delegates execution to the ConsignCloudClient's voidSale method, returning the JSON-serialized result.
    case 'void_sale':
      return { content: [{ type: 'text', text: JSON.stringify(await client.voidSale((args as any).id), null, 2) }] };
  • Input schema validation for the 'void_sale' tool, requiring a single 'id' parameter of type string.
    inputSchema: {
      type: 'object',
      properties: {
        id: { type: 'string', description: 'Sale ID' },
      },
      required: ['id'],
    },
  • src/server.ts:125-135 (registration)
    Registration of the 'void_sale' tool in the createTools() function, including name, description, and input schema.
    {
      name: 'void_sale',
      description: 'Void a sale',
      inputSchema: {
        type: 'object',
        properties: {
          id: { type: 'string', description: 'Sale ID' },
        },
        required: ['id'],
      },
    },
  • Core implementation in ConsignCloudClient: performs HTTP POST to `/sales/${id}/void` endpoint and converts the API response using convertSaleResponse.
    async voidSale(id: string): Promise<Sale> {
      const response = await this.client.post(`/sales/${id}/void`);
      return this.convertSaleResponse(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. 'Void a sale' implies a destructive mutation (likely irreversible), but it does not specify permissions required, side effects (e.g., inventory restocking, financial adjustments), error conditions, or response format. For a mutation tool with zero annotation coverage, this is a significant gap in transparency, though not contradictory.

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 'Void a sale' is extremely concise—a single phrase with zero wasted words. It is front-loaded with the core action, making it easy to parse quickly. Every word earns its place by directly conveying the tool's purpose 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?

Given the tool's complexity as a destructive mutation with no annotations and no output schema, the description is incomplete. It fails to address critical aspects like what 'void' means operationally, what happens post-void (e.g., status changes, notifications), or error handling. For a tool that likely impacts financial or inventory systems, this lack of detail is inadequate for safe and effective 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?

The input schema has 100% description coverage, with the 'id' parameter documented as 'Sale ID'. The description adds no additional meaning beyond this, such as format examples (e.g., numeric vs. string) or validation rules. Since the schema does the heavy lifting, the baseline score of 3 is appropriate, as the description does not compensate but also does not detract.

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 'Void a sale' clearly states the verb ('void') and resource ('sale'), providing a basic understanding of the tool's function. However, it lacks specificity about what 'void' entails (e.g., cancellation, reversal, or marking as invalid) and does not differentiate it from sibling tools like 'delete_item' or 'update_batch_status', which might involve similar destructive operations. This makes it vague but not misleading.

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 does not mention prerequisites (e.g., sale must be recent or unprocessed), exclusions (e.g., cannot void completed shipments), or related tools like 'get_sale' for verification. With sibling tools including various 'get', 'list', 'create', and 'update' operations, the lack of context leaves the agent uncertain about appropriate usage scenarios.

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