Skip to main content
Glama
@cmssy/mcp-server

@cmssy/mcp-server

Official

Update price list

update_price_list
Destructive

Change a price list's name, percent discount or markup, active date window, and published sales channels. Adjust how catalogue prices apply to buyers; fixed prices are set separately.

Instructions

Rename a price list, change its percentOff (-1000 to 99.99, 2 decimals, negative = a markup; it prices every product the list holds no fixed price for) its startsAt / endsAt window (null clears a bound), or the sales channels it is published to (channels replaces the whole set, [] unpublishes it from every channel, leave it out to keep). Fixed prices are changed with set_price_list_entry / set_price_list_entries. Carts already priced from the list keep their prices until the buyer adds again; orders keep theirs.

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": {
      "id": "<id>"
    },
    "name": "update_price_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe price list's id (from list_price_lists)
nameNoNew unique name
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.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false and destructiveHint=true, and the description reinforces blast radius by noting that channels replaces the whole set and [] unpublishes the list everywhere. It also adds useful downstream effects (carts keep prices until re-add, orders keep theirs) that the annotations cannot convey. That is real added context, though the description repeats the destructive semantics rather than explaining permission or failure behavior in depth.

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?

Front-loaded with the set of mutable fields and reads as a compact enumeration, with no filler sentences. The nested parentheticals (percentOff range, channels set semantics) make single sentences dense and slightly harder to scan, but nothing is wasted.

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

Completeness4/5

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

For a destructive partial-update tool with no output schema, the definition covers the field semantics, the reference sources for ids and channel keys (list_price_lists, list_sales_channels), the error codes for channel clashes, and the pricing windows' effect. Only post-call verification/response shape is unaddressed, and that is minor here.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3; the description still adds meaning beyond the schema for the most consequential field, stating that channels replaces the entire set and that omitting it keeps the current channels – detail the schema description only partially covers. The percentOff and null-clears semantics are largely duplicated from the schema, so it does not go far beyond the structural data.

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?

Names a specific verb+resource and enumerates exactly what can change: name, percentOff, startsAt/endsAt, channels. It also explicitly scopes out fixed-price changes by naming set_price_list_entry / set_price_list_entries as the tools for those, so an agent can separate it from the closest siblings.

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 for the main ambiguity ('Fixed prices are changed with set_price_list_entry / set_price_list_entries') and states the keep-vs-clear-vs-empty conventions. It doesn't discuss other alternatives or prerequisites (e.g. permissions), but the when-to-use signal is solid.

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