Skip to main content
Glama
@cmssy/mcp-server

@cmssy/mcp-server

Official

Set price list entries

set_price_list_entries
Destructive

Upserts up to 1,000 fixed prices on a price list for ERP or spreadsheet imports; each row replaces that product/variant/currency entry and the whole call fails if any row is invalid.

Instructions

Upsert up to 1000 fixed prices on a price list in one call (an ERP or spreadsheet import). Each row is one product (no variantKey) or one variant of a product with variants (variantKey required there), price in minor units of the row's currency (currency omitted = the default currency; an additional currency writes that currency's own row) with optional volume breaks and optional minQuantity / maxQuantity order bounds; a row replaces the whole entry already set for the same product/variant and currency, so bounds it had are cleared unless the row re-sends them (read them with get_price_list); every other entry stays. All or nothing: one invalid row refuses the whole call and the error names every bad row by index. Fixed prices override the list's percentOff. Never removes entries - use remove_price_list_entries for that.

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": {
      "priceListId": "<priceListId>",
      "entries": "<entries>"
    },
    "name": "set_price_list_entries"
  }
}

Input Schema

NameRequiredDescriptionDefault
entriesYesUp to 1000 fixed prices
priceListIdYesThe price list's id (from list_price_lists)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.73.2

TDQS

A4.6/5.0
Behavior5/5

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

Annotations only say readOnlyHint=false and destructiveHint=true; the description explains exactly what is destructive — a row replaces the whole entry and clears quantity bounds unless re-sent, while every other entry survives. It adds all-or-nothing atomicity, error reporting by row index, and the fact that fixed prices override the list's percentOff.

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 action and the row count, and nearly every clause carries real information (replace semantics, minor units, atomicity, alternatives). It is a single dense semicolon-chained sentence, which costs some scannability for a definition this information-heavy.

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 destructive bulk-upsert with no output schema, the description covers the parts an agent could get wrong: replace-vs-merge behavior, cleared bounds, currency row isolation, minor-unit pricing, and the all-or-nothing failure mode with per-row errors. Little is left to inference.

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 spells out recordId, variantKey, currency, tiers and quantity bounds in detail, so the description's parallel notes largely restate structured data. It does add a little framing (one row per product or variant, currency omitted means default), but nothing the schema does not already carry, so the baseline 3 applies.

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 ("Upsert up to 1000 fixed prices on a price list in one call") plus the intended scenario (ERP or spreadsheet import). It also distinguishes itself from remove_price_list_entries and get_price_list in the same paragraph, so an agent can pick it out of a crowded sibling set.

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?

Explicitly routes to alternatives: read existing bounds with get_price_list, use remove_price_list_entries when deletion is intended, and the tool itself never removes entries. It also states the trigger context (bulk import of fixed prices) so the agent knows when this is the right call.

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