Skip to main content
Glama
modellers

ConsignCloud MCP Server

by modellers

get_sale

Retrieve detailed information about a specific consignment sale, including transaction data and item specifics, to track business operations.

Instructions

Get details of a specific sale

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesSale ID

Implementation Reference

  • src/server.ts:114-124 (registration)
    Registration of the 'get_sale' tool including name, description, and input schema requiring a sale ID.
    {
      name: 'get_sale',
      description: 'Get details of a specific sale',
      inputSchema: {
        type: 'object',
        properties: {
          id: { type: 'string', description: 'Sale ID' },
        },
        required: ['id'],
      },
    },
  • MCP server tool handler that extracts the sale ID from arguments and delegates to client.getSale(), returning the result as JSON text content.
    case 'get_sale':
      return { content: [{ type: 'text', text: JSON.stringify(await client.getSale((args as any).id), null, 2) }] };
  • Implementation of getSale in the ConsignCloudClient class: performs API GET request to `/sales/${id}` and converts the response data using convertSaleResponse for currency handling.
    async getSale(id: string): Promise<Sale> {
      const response = await this.client.get(`/sales/${id}`);
      return this.convertSaleResponse(response.data);
    }
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure but offers minimal information. It implies a read operation ('Get details'), which suggests it's likely safe and non-destructive, but doesn't specify permissions, rate limits, or response format, leaving significant gaps in understanding how the tool behaves.

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 extremely concise with a single, direct sentence that front-loads the core purpose without any wasted words. It efficiently communicates the essential action, making it easy to parse and understand 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?

Given the tool's simplicity (one parameter, no output schema) and lack of annotations, the description is incomplete. It doesn't explain what details are returned, potential errors, or how it fits into the broader context of sales management, leaving the agent with insufficient information for robust 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 description adds no meaning beyond the input schema, which has 100% coverage and clearly documents the single required 'id' parameter. Since the schema does the heavy lifting, the baseline score of 3 is appropriate, as the description doesn't compensate but also doesn't detract.

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 ('details of a specific sale'), making it easy to understand what the tool does. However, it doesn't explicitly differentiate from sibling tools like 'get_item' or 'get_account', which follow a similar pattern, so it misses the highest score.

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 when to choose 'get_sale' over 'list_sales' for multiple sales or 'search_suggest' for broader queries, leaving the agent to infer usage from context 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