untappd-mcp-server

get_venue_foursquare_lookup

Resolve a Foursquare venue ID to its corresponding Untappd venue, enabling access to Untappd venue data from Foursquare identifiers.

Instructions

Resolve a Foursquare venue ID to its Untappd venue (bridge between Foursquare data and Untappd venue tools)

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "foursquare_id": "<foursquare_id>"
    },
    "name": "get_venue_foursquare_lookup"
  }
}

Input Schema

Name	Required	Description	Default
`foursquare_id`	Yes	Foursquare venue ID in v2 MD5-hash format (v3 numeric IDs will not work)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.0.0Jul 29, 2026

TDQS

A3.7/5.0

Behavior2/5

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

With no annotations, the description carries the full burden. It only states the basic mapping behavior, omitting important details such as error handling (e.g., if the ID is invalid or not found), return shape, or any destructive actions. The description is too sparse for complete transparency.

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 a single, concise sentence that effectively communicates the tool's purpose. It is front-loaded and contains no unnecessary words.

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?

For a simple one-parameter tool, the description is adequate but incomplete: it does not mention what the output is (presumably an Untappd venue), and there is no output schema. Given the lack of annotations, adding a brief note about the return value would improve completeness.

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, but the description adds a crucial constraint: the foursquare_id must be in v2 MD5-hash format, specifically noting that v3 numeric IDs will not work. This goes beyond the schema description and guides correct input.

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 clearly states the tool resolves a Foursquare venue ID to its Untappd venue, positioning it as a unique bridge between platforms. This distinguishes it from sibling tools like venue_search or get_venue_info, which operate entirely within Untappd.

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 description implies usage when a Foursquare venue ID is known and an Untappd venue is desired, but it lacks explicit guidance on when to use this versus alternatives like venue_search. No exclusion criteria or examples are provided.

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