Skip to main content
Glama
@cmssy/mcp-server

@cmssy/mcp-server

Official

Set price list entry

set_price_list_entry
Destructive

Set a fixed price, optional volume tiers, and quantity bounds for one product or variant in a price list, choosing the currency row and replacing any existing entry.

Instructions

Set a price list's fixed price for one product, or one variant of a product with variants (variantKey required there - a list prices each variant on its own, never the product as a whole; omit it for a product without variants). currency picks the row: omitted is the default-currency row, an additional currency writes that currency's own row, which prices only carts in it. The fixed price (minor units of the row's currency, with optional volume breaks) overrides the list's percentOff for that product or variant; replaces the entry already set for it as a whole, so an existing minQuantity / maxQuantity left out of the call is cleared - read it with get_price_list and re-send it to keep it. For many rows use set_price_list_entries.

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": {
      "recordId": "<recordId>",
      "price": "<price>",
      "priceListId": "<priceListId>"
    },
    "name": "set_price_list_entry"
  }
}

Input Schema

NameRequiredDescriptionDefault
priceYesFixed unit price in minor units of the row's currency (the default currency when currency is omitted; 4900 = 49.00), above 0. Replaces the catalogue price and the list's percentOff for this product or variant; it may be above the catalogue price (a contract price).
tiersNoThe entry's own volume breaks, minor units, each cheaper than the one below it and than the entry price. Omitted = none; the catalogue breaks do not carry over to a fixed price.
currencyNoThe row's currency: one of the workspace's additional currencies writes that currency's row; omit it (or send the default currency) for the default row. Each currency's row keeps its own price, tiers and quantity bounds, and prices only carts in its currency - nothing is converted
recordIdYesProduct record id
variantKeyNoThe variant's key - required for a product with variants (a list prices each variant separately, never the product as a whole); omit for a product without variants
maxQuantityNoLargest quantity (1-999) a buyer on this list may order, never above the cart's per-item cap; at least minQuantity. Omitted or null = no maximum beyond that cap. A write replaces the whole entry: re-send the bound it has or it is cleared.
minQuantityNoSmallest quantity (1-999) a buyer on this list may order of this product or variant. Omitted or null = no minimum. A write replaces the whole entry: re-send the bound it has or it is cleared.
priceListIdYesThe price list's id (from list_price_lists)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.73.2

TDQS

A4.8/5.0
Behavior5/5

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

Annotations declare destructiveHint=true and readOnlyHint=false; the description goes well beyond that by naming exactly what is lost — the entry is replaced as a whole, so an omitted minQuantity/maxQuantity is cleared — and by stating that the fixed price overrides the list's percentOff and that catalogue volume breaks do not carry over. It also explains the non-obvious scoping effect of a currency row ('prices only carts in it').

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?

Content is front-loaded with the core operation first, then variant/currency rules, then the destructive replacement warning. It is a single dense paragraph with heavily stacked parentheses, which slightly hurts scannability, but no sentence is filler.

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 an 8-parameter destructive mutation with no output schema, the description covers the decisions that matter: variant handling, currency row selection, override semantics, and data loss on replacement. It also points to get_price_list for the read needed to preserve existing bounds.

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, but the description adds interpretation the schema leaves implicit: the relationship between variantKey presence and product type, and the rule that currency selects which row is written and that each currency row keeps its own price/tiers/bounds. It does not add much on tiers or quantity bounds beyond what the schema already documents.

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?

Opens with a specific verb+resource and scope: 'Set a price list's fixed price for one product, or one variant of a product with variants.' It explicitly separates itself from set_price_list_entries ('For many rows use set_price_list_entries') and from get_price_list, so an agent can pick it without opening the schema.

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

Usage Guidelines5/5

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

Gives concrete when-to-use rules: variantKey is required for products with variants and must be omitted otherwise; currency omitted writes the default-currency row while an additional currency writes that currency's own row; and bulk use routes to set_price_list_entries. The read-modify-write path (get_price_list then re-send) is spelled out rather than inferred.

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