Skip to main content
Glama
chrischall

untappd-mcp

by chrischall
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Get Untappd brewery detail

untappd_brewery_info
Read-onlyIdempotent

Get a brewery's complete profile by its Untappd ID: description, location, type, rating, total check-ins, and popular beers. Use the ID from a brewery search to access full details.

Instructions

Get full detail for a brewery by its Untappd brewery id: description, location, type, rating, total check-ins, and popular beers. Get an id from untappd_search_brewery. Read-only.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
viewNoResponse shape: "compact" (default) drops fields the response already carries elsewhere; "full" returns every field this server understands. compact also asks Untappd for its own slim record, dropping the embedded activity/list blocks; "full" returns everything.
brewery_idYesUntappd brewery id

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. Changed2 schema fields changedv1.10.1
    • removedInput schema / properties / compact
      Removed value: -{
-  "description": "Return a slimmer record without embedded activity (default false)",
-  "type": "boolean"
-}
    • addedInput schema / properties / view
      Added value: +{
+  "description": "Response shape: \"compact\" (default) drops fields the response already carries elsewhere; \"full\" returns every field this server understands. compact also asks Untappd for its own slim record, dropping the embedded activity/list blocks; \"full\" returns everything.",
+  "enum": [
+    "compact",
+    "full"
+  ],
+  "type": "string"
+}
  3. First observedv0.0.0

TDQS

A4.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint, so the safety profile is well covered. The description adds the returned fields and the id-dependency, but doesn't disclose pagination, error behavior, or the behavioral effect of the view parameter beyond what the schema already says.

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?

Two tight sentences with no filler. The core behavior and returned fields are front-loaded, followed by the dependency and read-only note.

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?

All required parameters are documented in the schema, and the description supplies the id source and the main returned content. A minor gap is the lack of explicit handling for unknown or invalid brewery ids, but this is low-risk for a read-only lookup backed by rich annotations.

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?

The schema covers 100% of parameters, including a detailed description of the view enum. The description adds meaningful resolution guidance with 'Get an id from untappd_search_brewery', which helps the agent supply brewery_id correctly.

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?

States a specific action ('Get full detail'), the exact resource (brewery by Untappd id), and enumerates the returned content: description, location, type, rating, check-ins, and popular beers. This clearly distinguishes it from sibling beer, venue, and user tools.

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?

Explicitly tells the agent to obtain the brewery id from untappd_search_brewery, which is a concrete prerequisite and usage signal. It doesn't spell out exclusions versus untappd_brewery_beers or untappd_beer_info, but the detail-focused wording makes the intended use clear.

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