Skip to main content
Glama

Get product pricing

get_product_pricing
Read-only

Everything about ONE product's prices in one call: its own price, old price and currency; the price-list rows (other currencies); per-channel price overrides (platform, currency, price); the channel price rules that apply where there is no override (channelPriceRules); wholesale quantity breaks per currency; the purchase cost with its currency (a bundle's cost is derived from its components and cannot be set on it); and the markup over cost per sale currency (marginPercent = price ÷ cost − 1, in percent; not a margin on the price) — the cost crossed at the workspace's stated rate, null with missingRate true when no rate is stated. Read-only. Use search_products for the id; call it before set_product_channel_price, set_product_price_tiers or upsert_product_prices so you change the right row, and after a change to confirm it. For a whole group of products use preview_bulk_price_change.

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_product_pricing"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe product id returned by search_products or get_product — never a SKU or a name.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare readOnly/non-destructive, so safety is covered; the description goes well beyond that by defining the marginPercent formula and warning it is not a margin on price, disclosing null with missingRate true when no rate is stated, and explaining that a bundle's cost is derived from components and cannot be set on it. These are non-obvious behavioral traits an agent could not get from the annotations.

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 scoping statement is front-loaded and every clause carries information (return contents, formula, edge-case null), with the usage guidance cleanly following. It is dense and long for a one-parameter tool, but with no output schema the enumeration earns its space; only the redundant 'Read-only' is wasted.

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?

With no output schema, the description fully carries the return-value burden by describing each price facet, the currency handling, and the markup/cost edge case. Combined with the caller-side ordering guidance, nothing an agent needs to invoke and interpret this tool is missing.

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?

There is a single parameter and schema coverage is 100%; the schema already states it is the product id from search_products or get_product and never a SKU or name. The description only restates the search_products pointer, adding little semantics beyond the schema, so the baseline 3 applies.

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 scope ('Everything about ONE product's prices in one call') and then enumerates exactly which price facets are returned: own price, price-list rows, channel overrides, channel price rules, tier breaks, cost, and markup. An agent can distinguish this from get_product or search_products without opening any 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?

It names the lookup dependency ('Use search_products for the id'), specifies call ordering relative to set_product_channel_price, set_product_price_tiers and upsert_product_prices (before to target the right row, after to confirm), and routes bulk work to preview_bulk_price_change. Both when-to-use and which-alternative are explicit.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources