Skip to main content
Glama

Calder Vale Supply Inventory

price_quote

Read-only

Price a quantity of one item: unit price at the matching tier, line total, stock on hand and lead time.

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>",
      "quantity": "<quantity>"
    },
    "name": "price_quote"
  }
}

Input Schema

NameRequiredDescriptionDefault
skuYesItem code such as CV-200.
quantityYesUnits required.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already establish readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds value beyond that by disclosing the response shape (unit price at the matching tier, line total, stock on hand, lead time) and implicitly signaling tier-based pricing and single-item scope, though it says nothing about behavior on invalid SKUs or missing pricing tiers.

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?

A single sentence with the action front-loaded and the outputs enumerated afterward. Every clause earns its place; nothing is padding or restated from the title.

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?

With no output schema, the description usefully lists the four returned values, and with only two fully documented parameters there is little left to cover. Missing are currency/units and error behavior for unknown SKUs, which keeps it short of a 5 for a pricing tool.

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?

Schema description coverage is 100%, so both sku ('Item code such as CV-200') and quantity ('Units required') are already documented and the baseline is 3. The description adds only the nuance that quantity drives tier selection and that sku refers to a single item; it gives no format, currency, or boundary guidance beyond the schema.

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 a concrete verb and resource ('Price a quantity of one item') and enumerates exactly what comes back (unit price at matching tier, line total, stock on hand, lead time). That makes it distinguishable from inventory_lookup (stock data only) and order_history (past orders), though the overlap with inventory_lookup on 'stock on hand' is not explicitly addressed.

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 only implied: the phrase 'one item' hints that a multi-line cart requires repeated calls, but there is no explicit when-to-use, when-not-to-use, or alternative routing among the sibling tools. An agent must infer that this is the pricing entry point rather than inventory_lookup.

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