Skip to main content
Glama
@cmssy/mcp-server

@cmssy/mcp-server

Official

Set company price list

set_company_price_list
Destructive

Assign a price list to a company so every member pays that list; pass null to unassign. Use only for company records, not individual customers.

Instructions

Assign a price list to a company record; null unassigns. Every member of the company pays this list - one list per buyer, and a member's own list is ignored while they belong to the company. A company without a list leaves its members on catalogue prices. Refused for a record that is not a company (a model with the Company capability) - for a customer use set_customer_price_list. Returns the record id and its priceListId.

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

Input Schema

NameRequiredDescriptionDefault
recordIdYesThe company record's id (a record of a model with the Company capability; a customer's company.id)
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.6/5.0
Behavior4/5

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

Adds substantial context beyond the annotations: the effect propagates to every company member, a member's own list is ignored while they belong to the company, and a company with no list falls back to catalogue prices. It also discloses the refusal condition and the return payload, though it does not spell out what happens to the member's prior individual list once unassigned.

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?

Four tight sentences, front-loaded with the core action and the null variant, then consequences, then the refusal/alternative. Dense but essentially waste-free; only the return-value sentence is mildly expendable.

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 two-parameter mutation with no output schema, it covers preconditions, inherited effects, fallback behavior, refusal routing and return values. An agent has everything needed to call it correctly and interpret the result.

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 percent, so the baseline is 3, but the description adds downstream meaning the schema does not: recordId must identify a Company-capability model, and priceListId governs the price every member pays. The id-source hint for list_price_lists is largely duplicative of the schema.

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 ('Assign a price list to a company record') plus the null-unassign variant, and explicitly names the sibling it is not (set_customer_price_list). An agent can separate it from set_customer_price_list and set_company_price_display_mode without opening a 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 the trigger condition (record must be a company, i.e. a model with the Company capability), the negative case with an explicit redirect ('for a customer use set_customer_price_list'), and the null semantics for unassignment. Both when-to-use and when-not-to-use are covered.

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