Skip to main content
Glama
@cmssy/mcp-server

@cmssy/mcp-server

Official

Create price list

create_price_list

Create a price list with a percent discount or markup off catalogue prices plus optional fixed prices per product, then assign it to companies or customers and publish it to sales channels.

Instructions

Create a price list: a percent off the catalogue (percentOff, -1000 to 99.99 with 2 decimals, default 0; negative = a markup) plus fixed prices per product or variant added with set_price_list_entry / set_price_list_entries. A fixed price overrides the percent for its product or variant; every other product gets the catalogue price minus percentOff. Then assign it to a company (set_company_price_list) or to a customer without a company (set_customer_price_list) - each buyer has one list: a company's members pay the company's list. startsAt / endsAt limit when it prices; outside that window its buyers pay catalogue prices. channels publishes it to sales channels by key: storefronts sending that channel are priced from it (a buyer's own or company list still wins for every product it prices), and anyone can read the prices of a list published to a PUBLIC channel.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "name": "<name>"
    },
    "name": "create_price_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesThe list's name, unique in the workspace (e.g. 'Gold')
endsAtNoISO date-time the list stops pricing buyers at, later than startsAt. null clears it (no end); leave it out to keep it. Outside its window a list prices nobody: its buyers pay catalogue prices.
channelsNoKeys of the sales channels to publish the list to (from list_sales_channels), at most 20. A channel takes one undated base list plus dated lists whose windows do not overlap; a clash is refused (CHANNEL_BASE_TAKEN or CHANNEL_WINDOW_OVERLAP). Anyone can read the prices of a list published to a PUBLIC channel.
startsAtNoISO date-time the list starts pricing buyers from. null clears it (priced from now on); leave it out to keep it.
percentOffNoPercent taken off the catalogue price (and every volume break) of each product the list holds no fixed price for: -1000 to 99.99, at most two decimals (12.5 = 12.5% off). A negative value is a markup above the catalogue (-10 = 10% more). 0 = the list prices only through its fixed prices.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.73.2

TDQS

A4.4/5.0
Behavior5/5

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

Annotations only declare readOnlyHint=false and destructiveHint=false; the description goes far beyond that by disclosing the pricing precedence rule (fixed price beats percent for that product, everything else gets catalogue minus percentOff), the startsAt/endsAt window behavior (outside it buyers pay catalogue prices), and the channel-publishing conflict conditions with concrete error codes CHANNEL_BASE_TAKEN and CHANNEL_WINDOW_OVERLAP. It also notes that publishing to a PUBLIC channel makes prices world-readable, a material side effect not present in the annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Purpose and the core percent-vs-fixed model are front-loaded, and the long single paragraph carries dense, non-filler content. It runs together several distinct concerns (pricing model, assignment, scheduling, channel publishing) that would scan better as separated clauses, and some of the parameter detail duplicates the schema.

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

Completeness5/5

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

For a five-parameter create tool with no output schema, the description covers the full lifecycle an agent needs: how pricing is computed, what overrides what, how time windows disable pricing, how assignment works, and how channel publication behaves. The only unstated item is what the call returns (e.g. the new list id) for chaining into set_price_list_entry, which is minor given the otherwise thorough workflow coverage.

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% and the schema already documents the percentOff range, the negative-as-markup convention, the null-clears/omit-keeps semantics for startsAt and endsAt, and the channel conflict codes. The description mostly restates those same facts; its only genuinely additive detail is that percentOff defaults to 0 and how percentOff interacts with fixed entries, so the baseline 3 for full schema coverage is appropriate.

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

Purpose5/5

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

States a specific verb and resource ("Create a price list") and immediately defines the object model: a percent-off catalogue plus fixed per-product/variant overrides. It explicitly separates itself from sibling tools by naming set_price_list_entry, set_company_price_list, set_customer_price_list, and list_sales_channels with the role each plays, so an agent can tell what this tool does and does not do.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives clear routing guidance: create the list here, add fixed prices with set_price_list_entry/set_price_list_entries, then assign via set_company_price_list or set_customer_price_list, and warns that each buyer has one list. The only gap is no guidance on when to prefer a price list over the sibling create_discount, or when creating an unattached list is pointless.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools