pricing-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PRICING_MCP_DATA | No | Path to a directory containing your own pricing data files, using the same four files as the bundled dataset. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_productsA | List SKUs with tier, pack size, current price and unit cost, plus the pricing policy. category: optional filter, one of whole_bean, ground, cold_brew. |
| get_price_elasticityA | Estimate how sensitive a SKU's unit sales are to price, from 52 weeks of sales. Returns the elasticity, a 95% confidence interval, R², and a confidence label. |
| simulate_price_changeA | Project weekly units, revenue and gross margin if a SKU moves to new_price. Uses the SKU's estimated elasticity. Read the returned assumptions before relying on it. |
| check_price_guardrailsA | Check a proposed price against the pricing policy. Hard rules (minimum margin, maximum change per move) produce "block". The soft rule (competitor price index band) produces "warn". Otherwise "pass". |
| check_price_ladderA | Find price-ladder breaks in a category. Flags bigger packs that cost more per ounce, and higher tiers priced too close to or below lower tiers. |
| competitor_price_indexB | Compare each SKU's price with the median competitor price, against its tier's target band. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 6 tools
Each tool occupies a distinct analytical niche: elasticity estimation, simulation, policy guardrails, internal ladder checks, and competitor benchmarking. The three 'check/compare' tools could look similar at a glance (guardrails vs ladder vs competitor index), but their descriptions clearly separate hard policy rules, internal consistency, and external market position.
Five of six tools follow a clean verb_noun pattern (list_products, get_price_elasticity, simulate_price_change, check_price_guardrails, check_price_ladder). The lone outlier, competitor_price_index, is a noun-only name but is still readable and unambiguous.
Six tools is well-scoped for a pricing decision-support server, with each tool covering a distinct step in the analyze-simulate-validate workflow. No filler or redundant tools.
The read/analyze/simulate/validate lifecycle is covered, including guardrails and ladder checks that agents would otherwise have to invent. The notable gap is the absence of any write or apply operation (e.g. commit a price change or record a decision), so the workflow ends at advice.