Skip to main content
Glama

Get customer price

get_customer_price
Read-onlyIdempotent

Retrieves final unit prices and line totals for a buyer's company at specified quantities by applying the lowest base, quantity-tier, or shared-catalogue price. Supports up to 50 line items.

Instructions

Final unit price and line total for the buyer's company at the given quantities, taking the lowest of base price, quantity tier price and the company's shared-catalogue price. Up to 50 lines. Prices are for this company 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": {
      "lines": "<lines>"
    },
    "name": "get_customer_price"
  }
}

Input Schema

NameRequiredDescriptionDefault
linesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely useful behavior: the three-way lowest-price rule, the implicit company scoping from the caller's identity, and the 50-line ceiling. It stops short of currency, rounding, or unknown-SKU handling.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three tight sentences, front-loading the returned value, then the pricing rule, then the scope and limit. No filler or restatement of the tool name.

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 single-parameter read tool with no output schema, the description covers what is returned and how it is computed, which is enough to call it correctly. Minor gaps remain around per-line response shape and behavior when a SKU is not priced for the company.

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 only one top-level parameter and the schema already constrains it (1-50 items, sku/qty required, qty bounds). The description reinforces the quantity meaning by saying tier prices apply 'at the given quantities' and the 50-line cap, but adds no format or error semantics beyond that.

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 names a specific outcome (final unit price and line total) for a specific scope (the buyer's company, at the given quantities) and even states the pricing rule applied (lowest of base, tier, shared-catalogue). This separates it from catalogue-lookup siblings like get_product or check_availability without needing their schemas.

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?

Usage is implied rather than stated: an agent can infer this is the tool for company-specific pricing on a basket of SKU/qty lines, but there is no explicit when-to-use or when-not guidance and no named alternative for list or negotiated pricing.

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