Skip to main content
Glama
chrischall

untappd-mcp

by chrischall
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Get Untappd beer detail

untappd_beer_info
Read-onlyIdempotent

Retrieve complete beer details by Untappd beer ID, including description, style, ABV, IBU, brewery, rating, check-in count, and optional recent activity. Read-only.

Instructions

Get full detail for a beer by its Untappd beer id (bid): description, style, ABV, IBU, brewery, rating, total check-in count, and — on view:"full" — recent activity. Get a bid from untappd_search_beer. Read-only.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bidYesUntappd beer id (bid)
viewNoResponse shape: "compact" (default) drops fields the response already carries elsewhere; "full" returns every field this server understands. compact asks Untappd for its own slim record, dropping the embedded recent-activity (media/check-in) block server side; "full" returns the whole record including that activity. No local projection — the beer fields themselves are identical on both rungs.

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 the embedded recent-activity lists (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 asks Untappd for its own slim record, dropping the embedded recent-activity (media/check-in) block server side; \"full\" returns the whole record including that activity. No local projection — the beer fields themselves are identical on both rungs.",
+  "enum": [
+    "compact",
+    "full"
+  ],
+  "type": "string"
+}
  3. First observedv0.0.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint, so the safe read behavior is covered. The description adds an explicit output-field list and the view:'full' recent-activity behavior, giving the agent a concrete sense of what the call returns beyond the schema; no contradiction with annotations.

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 short sentences front-load the purpose and output fields, then add the bid-source instruction and read-only note. Every sentence earns its place and there is no redundant elaboration.

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 simple lookup with robust annotations and a 100%-documented schema, the description supplies the missing output contract (fields returned) and the view-dependent variation. An agent has enough to select and invoke the tool correctly even without an output schema.

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% and the view parameter already has a thorough description of compact/full behavior and no local projection. The description contributes little beyond the bid provenance tip ('Get a bid from untappd_search_beer'), so the schema remains the primary source of parameter meaning.

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 specific verb and resource ('Get full detail for a beer'), enumerates the returned fields, and explicitly ties the id to untappd_search_beer. It is clear, but it doesn't explicitly contrast itself with the sibling untappd_beer_activity, which also covers beer activity, so sibling differentiation is left to the tool name and 'full detail' wording.

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

Usage Guidelines3/5

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

The only usage guidance is 'Get a bid from untappd_search_beer', which addresses how to obtain the input rather than when to prefer this tool over siblings such as untappd_beer_activity or untappd_brewery_info. The intended context is implied by 'full detail' but no exclusions or alternatives are stated.

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