Skip to main content
Glama
Sign In

IMPOSSIBREW

by uk.co.impossibrew.agent
OverviewDiscussionsAdmin

Where to buy

where_to_buy
Read-onlyIdempotent

One answer to "where can I buy IMPOSSIBREW?". Give a UK town or postcode (optional) and it returns the best buying options in order: direct from impossibrew.co.uk, Zapp rapid delivery in London (also Zapp on Deliveroo and Uber Eats), Ocado, Amazon, and verified pubs, shops and venues nearby with distances. Only the outward part of a postcode is looked up. Retailer stock and prices are not checked live.

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": "where_to_buy"
  }
}

Input Schema

NameRequiredDescriptionDefault
locationNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior4/5

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

Beyond the read-only and open-world annotations, it discloses the fixed ordering of buying options, distance reporting for nearby venues, outward-only postcode lookup, and the important limitation that stock and prices are not checked live. These details help prevent the agent from overstating availability or location precision.

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?

Three compact sentences front-load the user question and input, then describe the ordered results and finish with two material limitations. The retailer list is somewhat detailed but directly defines the result scope rather than adding promotional filler.

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 low-complexity, single-parameter read tool, the definition covers the trigger, accepted location forms, geographic scope, result channels and ordering, nearby distances, postcode behavior, and freshness limitations. Although there is no output schema, the enumerated results provide enough return-value context for correct invocation and expectation setting.

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

Parameters4/5

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

With 0% schema description coverage, the description supplies the essential meaning of location: it is optional, accepts a UK town or postcode, and uses only the postcode's outward portion. It does not explain what location defaults to when omitted or how unsupported locations are handled.

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 clearly identifies the task as answering where to buy IMPOSSIBREW and specifies the ranked mix of direct, delivery, retail, and nearby venue options. It does not explicitly distinguish this broader purchase-discovery tool from the sibling find_stockists.

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?

The opening question provides a clear use case, while 'Give a UK town or postcode (optional)' explains how to tailor the answer with local options. There is no explicit when-not guidance or routing to find_stockists for users who only want physical stockists.

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

All IMPOSSIBREW toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources