Skip to main content
Glama
@cmssy/mcp-server

@cmssy/mcp-server

Official

Set company price display mode

set_company_price_display_mode
Destructive

Set whether a company's buyers see prices as net (VAT added on top) or gross (VAT included). Applies to new carts only; null restores the net default.

Instructions

Set how the buyers of a company record read prices: net (VAT added on top) or gross (VAT inside); null falls back to the default, net for a company buyer. Applies to carts started after the change; existing carts and orders keep the mode they were priced in. Refused for a record that is not a company (a model with the Company capability). Returns the record id with its priceDisplayMode and taxRoundingMethod.

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>",
      "displayMode": "<displayMode>"
    },
    "name": "set_company_price_display_mode"
  }
}

Input Schema

NameRequiredDescriptionDefault
recordIdYesThe company record's id (a record of a model with the Company capability; a customer's company.id)
displayModeYesnet or gross; null falls back to the default, net for a company buyer

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.73.2

TDQS

A4.3/5.0
Behavior5/5

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

Annotations already flag readOnlyHint=false and destructiveHint=true, and the description goes well beyond them: it bounds the blast radius (only future carts are affected, existing carts and orders retain their mode), discloses the refusal condition, and states the return payload (record id with priceDisplayMode and taxRoundingMethod). Nothing about side effects or failure behavior is left to guesswork.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three sentences, front-loaded with the core action and its two values, then scope, then failure and return. Every sentence carries distinct information with no repetition or 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 two-parameter mutation with full schema coverage and no output schema, the definition supplies everything an agent needs: what changes, who is affected and who is not, when it errors, and what comes back. No meaningful gap remains.

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%, so both parameters are already documented, and the description's parameter-level content ('null falls back to the default, net for a company buyer', 'a model with the Company capability') largely restates the schema descriptions. It adds no syntax, format, or edge-case detail beyond what the schema provides, so the baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb ('Set') on a specific resource ('how the buyers of a company record read prices') and immediately defines the two values with their business meaning (net = VAT added on top, gross = VAT inside). It is clearly distinguishable from the adjacent price-list and tax-rounding siblings by describing the exact effect on buyer-facing prices, though it never names an alternative tool explicitly.

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 states the temporal scope of the change ('Applies to carts started after the change; existing carts and orders keep the mode they were priced in') and the precondition for success ('Refused for a record that is not a company'). That is strong when/when-not guidance, but it does not route the agent to any alternative tool for the cases where this one is refused or when the agent actually wants price lists or tax rounding.

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