Skip to main content
Glama
mcp-erp-server

mcp-erp-server

by aldemarluz

Get price for a customer

sales_get_price
Read-only

Retrieve a product's price for a customer's tier and check whether it is above the floor price.

Instructions

Price of a product for a customer's tier, and whether it is above the floor price.

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": {
      "sku": "<sku>",
      "customerId": "<customerId>"
    },
    "name": "sales_get_price"
  }
}

Input Schema

NameRequiredDescriptionDefault
skuYes
customerIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior3/5

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

The readOnlyHint annotation already establishes this is a safe read, so the description's extra value is the disclosure that a floor-price comparison is returned alongside the price — useful output context. It says nothing about currency, tax treatment, or what happens when the tier or SKU is unknown, which is the remaining gap given annotations cover safety.

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?

A single front-loaded sentence with no wasted wording; the price is stated first and the floor-price companion second. The brevity is somewhat under-specification rather than elegance, but nothing is padded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, no parameter descriptions, and only a readOnlyHint, the definition should explain the returned price's shape (amount and currency) and the floor-flag semantics. As written, an agent knows roughly what it gets but not enough to interpret the response.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must carry parameter meaning, but it only loosely maps 'product' and 'customer' to sku and customerId without format, case, or identifier-source guidance. An agent still has to guess what a valid SKU or customer ID looks like.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names the resource concretely — the price of a product for a customer's tier — and adds a distinguishing second output (the above-floor-price flag). It is not a sibling like sales_find_customer or sales_list_orders, though no sibling is named to reinforce that contrast.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

There is no when-to-use guidance, no prerequisites, and no mention of alternatives such as finance_receivables. The agent must infer from the name alone that this is the price-lookup path.

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