Skip to main content
Glama
@cmssy/mcp-server

@cmssy/mcp-server

Official

Delete price list

delete_price_list
Destructive

Permanently delete a price list and its fixed prices, unassign it from all companies and customers, and unpublish it from every sales channel. This cannot be undone.

Instructions

Delete a price list with all its fixed prices and unassign it from every company and customer it prices (see assignedCount in list_price_lists) - they pay catalogue prices from then on - and unpublish it from every sales channel it is published to (see channels). Orders keep the list name they were priced under. Cannot be undone.

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

Input Schema

NameRequiredDescriptionDefault
idYesThe price list's id (from list_price_lists)

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?

Beyond the annotations (destructiveHint=true, readOnlyHint=false), the description discloses exactly what is destroyed and what side effects occur: fixed prices are deleted, companies and customers are unassigned and fall back to catalogue prices, sales-channel publications are removed, and historical orders retain the list name. It also states the operation cannot be undone, which is critical context for a destructive tool.

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 description is a single dense sentence that front-loads the core action and then layers in the cascade effects. Every clause carries useful information, though the parenthetical references and long run-on structure make it slightly harder to scan than a more segmented presentation would be.

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?

For a one-parameter destructive tool with no output schema, the description covers the critical behavioral consequences thoroughly. It does not mention authorization requirements, error behavior if the id is invalid, or what the response contains, but the essential deletion semantics are complete.

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 coverage is 100% for the single 'id' parameter, and the schema already documents that the id comes from list_price_lists. The description does not add further meaning about the id parameter itself, so the baseline score of 3 is appropriate.

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 ('Delete a price list') and immediately scopes the operation by naming the cascading effects on fixed prices, company/customer assignments, and sales-channel publications. This distinguishes it clearly from siblings like remove_price_list_entries or update_price_list.

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?

The description makes the consequences explicit enough that an agent can infer this is the tool for removing an entire price list rather than individual entries or assignments. It does not explicitly name alternatives or state when not to use it, but the cascade details provide strong contextual guidance for selecting it.

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