Skip to main content
Glama

Lowest price for a bottle

best_price
Read-onlyIdempotent

Find a bottle by name and return its lowest current in-stock price across independent shops, with the shop and a link.

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": {
      "query": "<query>"
    },
    "name": "best_price"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesThe bottle, e.g. 'Brunello di Montalcino 2016 Mastrojanni'.

Output Schema

NameRequiredDescriptionDefault
foundYes
queryNo
bottleNo
best_offerNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Beyond the annotations, which already establish read-only, idempotent, non-destructive behavior, the description adds useful scope: prices are current and in-stock only, limited to independent shops, and the result includes the shop and a link. It does not cover details like currency or shipping, but it adds meaningful behavioral context.

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?

The description is a single, front-loaded sentence with no wasted wording. It efficiently conveys the lookup action, scope, and returned information.

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

Completeness5/5

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

For a simple, read-only lookup tool with rich annotations, complete parameter schema, and an output schema, the description is sufficient. It explains what the tool does and what the caller gets back, without redundantly restating structured data.

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% and the single query parameter is already fully described with an example. The description reinforces that the query is a bottle name, but it does not add constraints or format details beyond what the schema provides.

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 states a specific verb and resource: find a bottle by name and return its lowest current in-stock price across independent shops, including the shop and link. This clearly defines the operation, though it does not explicitly name or contrast with sibling tools such as bottle_offers or price_index.

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?

The description implies usage by saying it returns the lowest current in-stock price, which helps an agent understand the use case. However, it offers no explicit when-to-use or when-not-to-use guidance relative to alternatives like bottle_offers or price_index.

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