Skip to main content
Glama

punkapi_search_beers

Read-onlyIdempotent

Search craft beer recipes by name to find matching beers, with page and per_page controls for browsing results.

Instructions

Search craft beer recipes by name.

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

Input Schema

NameRequiredDescriptionDefault
pageNoPage number (default 1)
queryNoBeer name to search for
per_pageNoResults per page (max 25, default 10)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.11

TDQS

B3.1/5.0
Behavior2/5

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

Annotations already declare the tool as read-only, idempotent, open-world, and non-destructive, but the description adds no behavioral context beyond the basic purpose. It does not disclose match behavior, pagination behavior, or what happens if the optional query is omitted.

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 definition is a single front-loaded sentence with no redundant clauses. It is appropriately sized for a simple search tool.

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?

The tool is simple and the schema is rich, but with no output schema the description does not explain the return shape or result count. It also leaves ambiguous why query is optional for a search-by-name 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 coverage is 100%, so the parameter meanings are already well documented. The description reinforces that searching is by name, but adds no extra semantics for page, per_page, or optional query behavior.

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?

States a specific verb and resource ('Search craft beer recipes') plus a scope ('by name'), so the core purpose is clear. It does not explicitly distinguish itself from nearby siblings like punkapi_get_beer or punkapi_random_beer, though the search-by-name wording helps.

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?

Gives no explicit when-to-use or when-not-to-use guidance and does not name alternatives such as punkapi_random_beer, punkapi_get_beer, or untappd_search_beer. Any usage is only implied by the phrase 'search ... by name'.

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

Deploy Server

Other Tools