Skip to main content
Glama
chrischall

untappd-mcp

by chrischall
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Get a venue's verified beer menu (section-paged)

untappd_venue_menu
Read-onlyIdempotent

Retrieve a venue's full verified beer menu as a flat list, covering all menu sections via resumable paging.

Instructions

Return a venue's verified beer menu as a flat, compact list of beers. untappd_venue_info returns only the FIRST section of each menu (Untappd defaults the section list to one), so it silently under-reports any venue whose menu spans multiple sections — e.g. a 23-beer wall that comes back with 2 items. This tool forwards the section_limit / section_offset paging params venue/info echoes back but never receives, walks sections up to a per-call max_pages budget (respecting the ~100 calls/hour limit — it does NOT loop to completion in one call), and flattens to [{bid, name, brewery, style, abv, price, serving_type, menu, section}]. Like the sync tools it is resumable: when the budget runs out before full coverage it returns another_run_needed:true plus next_section_offset to pass back on the next call. truncated:true means the upstream returned no more sections short of total_count (e.g. it ignored the paging params) — not resumable. Get an id from untappd_search_venue. Read-only.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sortNoMenu sort key (e.g. 'publish_order', 'highest_rated'). Optional.
menu_idNoRestrict to a single menu id (from a prior result). Optional.
venue_idYesUntappd venue id
max_pagesNoAPI calls to spend THIS run — page budget, not page size (default 3). Resume with next_section_offset if another_run_needed.
section_limitNoSections fetched per API call — page size (default 50).
section_offsetNoSection offset to start from; pass a prior next_section_offset to resume (default 0).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.0.0
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  2. Addedv1.8.1

TDQS

A4.9/5.0
Behavior5/5

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

Annotations only provide readOnlyHint, openWorldHint, and idempotentHint. The description goes far beyond these by disclosing that the tool deliberately does not loop to completion in one call, respects a ~100 calls/hour budget, returns another_run_needed and next_section_offset for resumability, and explains what truncated:true actually means. It is consistent with the read-only and idempotent hints.

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 long but information-dense, with each sentence serving a purpose: purpose, sibling comparison, paging behavior, resumability, truncation semantics, and source id. The core result is front-loaded in the first sentence, and the technical details are ordered logically.

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 tool with no output schema, the description provides the return shape, paging semantics, rate-limit behavior, resumability contract, and truncation caveat. It also names the upstream source tool for the venue id. Given the tool's complexity, this is a complete and sufficient definition.

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?

Schema coverage is 100%, so the baseline is 3. The description adds meaningful extra semantics by explaining the lifecycle of section_limit/section_offset, defining max_pages as a per-run API-call budget rather than a page size, and describing how next_section_offset is used to resume. This warrants a 4.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a specific verb and resource: 'Return a venue's verified beer menu as a flat, compact list of beers.' It also explicitly contrasts itself with untappd_venue_info, which only returns the first menu section, making the tool's distinct role immediately clear.

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

Usage Guidelines5/5

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

It directly names the alternative and explains its deficiency: 'untappd_venue_info returns only the FIRST section of each menu... so it silently under-reports.' It also tells the agent where to get the required id ('Get an id from untappd_search_venue') and explains when this tool is resumable versus when truncated results are not resumable.

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