Skip to main content
Glama
@cmssy/mcp-server

@cmssy/mcp-server

Official

Create sales channel

create_sales_channel

Creates a sales channel with a unique public key, currency, price access, and display mode, enabling storefronts to sell products under channel-specific pricing and access rules.

Instructions

Create a sales channel, at most 20 per workspace; a duplicate key is refused. The channel prices nothing until a price list is published to it (create_price_list / update_price_list with channels): one undated base list plus dated lists whose windows do not overlap. Channel keys are public - any storefront can send one - so priceAccess decides who sees its prices and may buy through it. currency picks what the channel sells in (the default currency when omitted): its carts, orders, shipping and discounts are in it, and a product with no price in it is not sold there.

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": {
      "key": "<key>",
      "name": "<name>"
    },
    "name": "create_sales_channel"
  }
}

Input Schema

NameRequiredDescriptionDefault
keyYesWhat the storefront sends as channel: 1-40 lowercase letters and digits, words joined by - or _ (e.g. 'horeca'). Cannot change later; orders keep it.
nameYesDisplay name, e.g. 'HoReCa'
currencyNoThe currency the channel sells in: the workspace's default currency (or null) or one of its additional currencies (update_cart_config additionalCurrencies)
displayModeNoHow visitors and customers without a company read the channel's prices: net (VAT added on top) or gross (VAT inside). Default gross; a company buyer keeps their company's mode.
priceAccessNoWho sees the channel's prices and may buy through it: PUBLIC - anyone (default); MEMBERS - signed-in customers, and registration is open; COMPANY_MEMBERS - buyers of an approved company, the one to use for trade prices. Others get prices withheld and carts refused.

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?

Beyond the annotations (readOnlyHint=false, destructiveHint=false), the description discloses the quota ceiling, duplicate-key rejection, the fact that a fresh channel sells nothing until a price list is attached, the non-overlapping date-window rule, and that keys are publicly transmissible by any storefront. That is substantial operational context an agent could not infer from structured fields.

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?

The creation act and its limits are front-loaded, and every clause carries information. The second half is a dense, run-on chain of parentheticals (price lists, public keys, currency) that would read better split apart, 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 a five-parameter, non-destructive creation tool with no output schema and fully described parameters, the description covers limits, failure mode, immutability implications, downstream dependencies and per-parameter consequences. Nothing an agent needs in order to call it correctly appears to be missing.

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, and the description earns extra by explaining consequences rather than restating fields: currency governs the channel's carts, orders, shipping and discounts and makes unpriced products unsellable there, and priceAccess controls both price visibility and the ability to buy. It does not add anything for displayMode or name beyond the schema's own text.

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?

The description opens with a specific verb and resource ('Create a sales channel') and immediately scopes it with concrete limits ('at most 20 per workspace; a duplicate key is refused'). Together with the sibling names update_sales_channel / delete_sales_channel, an agent can distinguish this creation call from the rest of the family 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 Guidelines4/5

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

It gives an explicit prerequisite chain: the channel prices nothing until a price list is published to it, and it names the alternative tools that do that (create_price_list / update_price_list with channels), including the required shape of one undated base list plus non-overlapping dated lists. It stops short of stating when-not-to-create or how to handle the 20-channel limit, so it is clear context rather than a full routing rule.

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