Skip to main content
Glama
@cmssy/mcp-server

@cmssy/mcp-server

Official

Get price list

get_price_list
Read-only

Fetch a price list by ID with paginated fixed prices for products or variants; filter by product record or currency to inspect entries and spot removed records.

Instructions

Get one price list by id with a page of its fixed prices (entries, oldest first, at most 200 per page; pass nextCursor back as after for the next page, null on the last). An entry is a fixed unit price in minor units for one product (variantKey null) or one variant of a product with variants, with its own volume breaks (tiers), its order bounds (minQuantity / maxQuantity, null = none) and its currency (an additional currency's row names it; a default-currency row reads the product's currency); recordMissing true means the product or variant was removed and the entry prices nothing - remove it with remove_price_list_entries. Filter by recordId to see one product's entries. Read-only.

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": "get_price_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe price list's id (from list_price_lists)
afterNonextCursor from the previous page
firstNoEntries per page, at most 200
currencyNoThe currency whose rows to page; omit for the default currency's rows. overrideCountByCurrency names the currencies the list holds rows in
recordIdNoOnly the fixed prices for this product record

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.73.2

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, and the description adds substantial context beyond them: ordering ('oldest first'), hard page cap ('at most 200 per page'), the null-on-last-page signal, the meaning of recordMissing, and how currency rows are resolved. It also explains that a recordMissing entry prices nothing and should be cleaned up elsewhere, which is exactly the behavioral detail an agent needs before acting.

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 and no sentence is filler, so it earns its length for a tool with a non-trivial return shape. However, it is delivered as one dense run-on paragraph with heavy parenthetical nesting, which makes the pagination and recordMissing rules harder to scan than they need to be.

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 the description compensates fully by explaining the entry structure (unit price in minor units, variantKey, tiers, minQuantity/maxQuantity, currency) and the pagination contract. An agent can parse the response and page through results correctly without any additional documentation.

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 description coverage is 100%, so the schema already documents all five parameters. The description still adds meaning beyond it by tying 'after' to the previous nextCursor, explaining the null terminator, and clarifying the currency/recordId filtering intent, so it improves on the baseline rather than merely restating 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?

The description states a specific verb and resource ('Get one price list by id') and immediately scopes what comes back ('with a page of its fixed prices'), which distinguishes it from list_price_lists and the various set_* siblings without ambiguity.

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 gives clear operational context: how to paginate ('pass nextCursor back as after'), how to narrow to a single product ('Filter by recordId'), and it names the correct alternative for cleanup ('remove it with remove_price_list_entries'). It stops short of explicitly saying when to prefer this over list_price_lists or set_price_list_entries, so it is clear but not fully exhaustive.

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