Skip to main content
Glama

Get price

get_price

Price including shipping and VAT for the delivery country. This is exactly what the user pays.

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": {
      "proof": "<proof>",
      "country": "<country>"
    },
    "name": "get_price"
  }
}

Input Schema

NameRequiredDescriptionDefault
proofYesProof id (prf_...)
stateNoUS and Canada only: state or province (NY, CA, ON, BC, ...)
countryYesDelivery country, ISO code (NL, DE, US, ...)
postcodeNoPostcode or ZIP of the delivery address. Many countries need it for the shipping price (Spain, Canada, Indonesia, Vietnam, Japan, India, China and others): pass it when you know it, and ask the user for it when get_price says it is needed.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / postcode / description
      Previous value: -"Spain and Canada only: postcode, needed for the shipping price"New value: +"Postcode or ZIP of the delivery address. Many countries need it for the shipping price (Spain, Canada, Indonesia, Vietnam, Japan, India, China and others): pass it when you know it, and ask the user for it when get_price says it is needed."
  2. First observed

TDQS

B3.2/5.0
Behavior3/5

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

The description adds real semantic context by stating the returned figure is the final amount the user pays, VAT and shipping included. However, annotations declare readOnlyHint=false and idempotentHint=false, and the description does not explain why a price lookup is non-read-only or non-idempotent (e.g. prices are re-quoted each call), leaving an unexplained behavioral gap that no structured field resolves.

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?

Two short sentences, front-loaded with the resource and its scope, followed by an interpretation of the output. No filler, though the second sentence is somewhat redundant with the first.

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

Completeness3/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 must convey the return value; it does state composition (shipping, VAT) but not form (numeric amount, currency, whether a breakdown is returned). For a required-proof pricing call whose behavior is partly opaque via annotations, a bit more would help.

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 coverage is 100%, so the schema already documents proof, country, state and postcode, including the note that postcode may be needed. The description only echoes the country scoping and adds no extra meaning about the proof parameter or how the country/state/postcode interact.

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?

Names a specific resource (price) and scopes it precisely: total including shipping and VAT for the delivery country. It is clear what the tool computes, though it does not distinguish itself from any sibling because none of the listed siblings are pricing tools.

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?

No when-to-use guidance at all: nothing about when a price quote is appropriate (e.g. before place_order), whether it can be re-requested, or how it relates to other flow steps. The only usage-relevant hint, that postcode may be required, lives in the schema rather than the description.

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