Skip to main content
Glama
modellers

ConsignCloud MCP Server

by modellers

create_item

Add new inventory items to ConsignCloud by specifying title, price, category, and inventory type for consignment or retail operations.

Instructions

Create a new inventory item

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
titleYesItem title
descriptionNoItem description
tag_priceYesPrice in cents
categoryNoCategory ID
accountNoAccount ID (vendor/consignor)
inventory_typeNoType of inventory
splitNoSplit percentage (0-1)
quantityNoQuantity
locationNoLocation ID

Implementation Reference

  • Core handler function that implements the logic to create a new inventory item by converting currency values to API format (cents), making a POST request to the ConsignCloud /items endpoint, and converting the response back to store currency.
    async createItem(data: Partial<Item>): Promise<Item> {
      // Convert user input to API cents
      const apiData = {
        ...data,
        tag_price: data.tag_price ? this.convertToApiCents(data.tag_price) : undefined,
        cost: data.cost ? this.convertToApiCents(data.cost) : undefined,
      };
      const response = await this.client.post('/items', apiData);
      return this.convertItemResponse(response.data);
    }
  • src/server.ts:39-61 (registration)
    Registration of the 'create_item' tool in the tools array returned by createTools(), including name, description, and detailed input schema.
    {
      name: 'create_item',
      description: 'Create a new inventory item',
      inputSchema: {
        type: 'object',
        properties: {
          title: { type: 'string', description: 'Item title' },
          description: { type: 'string', description: 'Item description' },
          tag_price: { type: 'number', description: 'Price in cents' },
          category: { type: 'string', description: 'Category ID' },
          account: { type: 'string', description: 'Account ID (vendor/consignor)' },
          inventory_type: {
            type: 'string',
            enum: ['consignment', 'buy_outright', 'retail'],
            description: 'Type of inventory'
          },
          split: { type: 'number', description: 'Split percentage (0-1)' },
          quantity: { type: 'number', description: 'Quantity' },
          location: { type: 'string', description: 'Location ID' },
        },
        required: ['title', 'tag_price'],
      },
    },
  • MCP server request handler dispatch case for 'create_item' tool call, which invokes the client.createItem method and returns JSON response.
    case 'create_item':
      return { content: [{ type: 'text', text: JSON.stringify(await client.createItem(args as any), null, 2) }] };
  • TypeScript interface definition for Item, used as the basis for create_item input (Partial<Item>) and output.
    export interface Item {
      id: string;
      title: string;
      description: string | null;
      tag_price: number; // converted to store currency (e.g., ISK, USD)
      cost?: number; // converted to store currency
      category: string | null;
      account: string | null;
      inventory_type: 'consignment' | 'buy_outright' | 'retail';
      split: number; // 0-1
      quantity: number;
      status: string;
      location: string | null;
      batch: string | null;
      created: string;
      sold: string | null;
      custom_fields?: any[];
    }
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 states 'Create a new inventory item' which implies a write/mutation operation, but fails to mention permissions needed, whether creation is idempotent, error handling, or what happens on success (e.g., returns an item ID). This leaves significant gaps for an agent to understand the tool's behavior.

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 wasted words—'Create a new inventory item'—making it front-loaded and appropriately sized for its purpose. Every word earns its place without redundancy.

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 no annotations and no output schema, the description is incomplete for a mutation tool with 9 parameters. It lacks information on return values, error conditions, or behavioral nuances like whether 'quantity' defaults to 1 if omitted. This leaves the agent with insufficient context for reliable invocation.

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%, with all 9 parameters well-documented in the schema (e.g., 'tag_price' as 'Price in cents', 'inventory_type' with enum values). The description adds no additional parameter semantics beyond the schema, so it meets the baseline of 3 for high schema coverage without compensating 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 'Create a new inventory item' clearly states the action (create) and resource (inventory item), which is specific and unambiguous. However, it doesn't differentiate from sibling tools like 'create_account' or 'create_batch' beyond the resource name, missing explicit distinction in functionality 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?

The description provides no guidance on when to use this tool versus alternatives like 'update_item' or 'create_batch', nor does it mention prerequisites such as required account or category setup. It lacks context for distinguishing among creation tools in the sibling 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