Skip to main content
Glama
@cmssy/mcp-server

@cmssy/mcp-server

Official

List price lists

list_price_lists
Read-only

Lists the workspace's price lists by name with each list's discount or markup, active window, fixed-price overrides, assigned buyers and sales channels so you can see how buyers are priced.

Instructions

List the workspace's price lists (Gold, Silver, dealer tiers ...), by name: each with percentOff (percent off the catalogue, 2 decimals; negative = a markup), startsAt / endsAt and active (false outside that window: the list prices nobody and its buyers pay catalogue prices), overrideCount (fixed prices it holds), assignedCount (companies and customers it prices) and channels (the sales channels it is published to, with key and priceAccess). A list prices a buyer from a fixed price per product or variant where it has one, else the catalogue price minus percentOff. Read-only; entries are in get_price_list.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_price_lists"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.73.2

TDQS

A4.4/5.0
Behavior5/5

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

With annotations covering only read-only safety, the description goes well beyond them: it defines what active=false means behaviorally (list prices nobody, buyers pay catalogue), explains negative percentOff as a markup, and states the fixed-price-then-catalogue-price resolution rule. It also explicitly restates read-only, which is consistent with the annotations rather than contradicting them.

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 purpose is front-loaded in the first clause and every sentence carries information about returned fields. The middle stretch is a dense run-on packing six field definitions plus a pricing rule into one sentence, which costs some parseability, 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?

There is no output schema and no parameters, so the description must carry the return contract, and it does: percentOff, startsAt/endsAt, active, overrideCount, assignedCount, and channels with priceAccess are all defined. For a zero-arg read tool this is complete enough to use the result correctly.

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?

Zero parameters, so there is no parameter semantics to add; the baseline applies. The text instead documents the returned fields, which is useful but does not belong to this dimension.

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?

"List the workspace's price lists ... by name" states a specific verb, resource, and ordering, and it disambiguates from the sibling get_price_list by noting that entries live there. An agent can pick this tool over the many other list_* siblings 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 Guidelines3/5

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

The only routing signal is the closing pointer to get_price_list for entries; there is no explicit statement of when to call this versus create_price_list/update_price_list or the set_*_price_list assignment tools. Usage is implied by the "list" verb and zero-parameter shape rather than taught.

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