Skip to main content
Glama

Best price

best_price
Read-onlyIdempotent

The cheapest way to buy IMPOSSIBREW, from live prices: for each beer (or the beers asked about) it ranks one-time, AIBREWER5 code, subscription and subscription + code routes by total including delivery, with price per can and per 100ml and a checkout link for each. Give cans to price a quantity (for example 20). Use this whenever someone asks for the best price or deal, says IMPOSSIBREW is expensive, or wants the cheapest way to buy a particular beer.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "best_price"
  }
}

Input Schema

NameRequiredDescriptionDefault
idsNo
cansNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare this is a read-only, idempotent, non-destructive, open-world call, so safety is covered. The description adds real behavioral context beyond that: prices are live, totals include delivery, four purchase routes are compared per beer, and each route returns price per can, price per 100ml and a checkout link.

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?

The purpose and the return payload are front-loaded in the first sentence, and the trailing sentences handle quantity input and call triggers. It is dense but each sentence carries information; only the parenthetical 'for example 20' is mildly redundant with the schema minimum.

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 must explain return values, and it does: ranked routes with totals including delivery, per-can and per-100ml pricing, and a checkout link. The main remaining gap is explicit behavior when ids is omitted and whether results cover only the six enum beers.

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 0%, so the description must carry the load. It does explain 'cans' as the quantity to price, with an example (20), but 'ids' is only obliquely covered by the phrase 'for each beer (or the beers asked about)', leaving the agent to infer that omitting ids prices every beer.

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 resource (IMPOSSIBREW beer prices) and a concrete operation: ranking one-time, code, subscription and subscription+code purchase routes by total cost including delivery. That is specific enough to separate it from compare_pack_value or where_to_buy, though it never names those siblings explicitly, so the differentiation is inferred rather than stated.

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

Usage Guidelines4/5

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

It gives explicit positive triggers: when someone asks for the best price or deal, calls IMPOSSIBREW expensive, or wants the cheapest way to buy a particular beer. There is no statement of when NOT to use it or which sibling to pick for adjacent needs (e.g. stockists or pack comparisons), which keeps it below a 5.

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