Skip to main content
Glama
@cmssy/mcp-server

@cmssy/mcp-server

Official

Set customer price list

set_customer_price_list
Destructive

Assigns a price list to a B2C customer without a company, or unassigns it when null. Use it to set a VIP buyer's own list; customers in a company must be priced via set_company_price_list.

Instructions

Assign a price list to a customer without a company (a B2C VIP); null unassigns. One list per buyer: a customer in a company pays the company's list, so assigning to them is refused - assign the list to the company with set_company_price_list instead. Returns the customer with priceList (their own) and effectivePriceList (the one that prices them, source MEMBER or COMPANY).

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>",
      "priceListId": "<priceListId>"
    },
    "name": "set_customer_price_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe customer's id (from list_customers)
priceListIdYesThe price list's id (from list_price_lists); null unassigns

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.73.2

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already flag destructiveHint=true, and the description adds real context beyond them: null performs an unassignment (the destructive path), company-bound customers are refused, and the response returns both priceList and effectivePriceList with MEMBER/COMPANY source. That explains the side effects and the one-list-per-buyer invariant the annotations cannot convey.

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 primary action and its scope, then the constraint and alternative, then the return shape. It is dense (one long compound sentence plus a second), and the return-value detail could arguably be trimmed, but no sentence is filler.

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?

With no output schema, the description compensates by naming the returned fields and their meaning. For a two-parameter mutation with annotations present, the essential context—preconditions, side effects, return shape, alternative tool—is all covered; only permission/auth requirements are unaddressed.

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 both params are already documented, but the description adds meaning the schema lacks: the null value is framed as an unassignment action rather than a missing value, and it clarifies that priceList is the customer's own list while effectivePriceList may come from a company membership. Minor gain over the schema, but genuine.

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+resource (assign a price list to a customer) and narrows scope precisely to 'a customer without a company (a B2C VIP)', which immediately separates it from the company-oriented sibling. The 'null unassigns' clause signals the dual mode of the operation up front.

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 states the precondition (customer must not belong to a company), the refusal behavior when violated, and names the correct alternative: 'assign the list to the company with set_company_price_list instead'. It also covers the unassign case via null, so both usage modes are routed.

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