Skip to main content
Glama
Sign In
Restaurant Booking MCP Server

Restaurant Booking MCP Server

by samwang0723
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get_restaurant_details

Retrieve comprehensive restaurant details such as reviews, photos, and opening hours using the Google Places ID. Supports multiple locales for accurate, localized information.

Instructions

Get detailed information about a specific restaurant including reviews, photos, and opening hours

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": {
      "placeId": "<placeId>"
    },
    "name": "get_restaurant_details"
  }
}

Input Schema

NameRequiredDescriptionDefault
localeNoLocale for restaurant details (e.g., "en" for English, "zh-TW" for Traditional Chinese, "ja" for Japanese, "ko" for Korean). Affects restaurant names, reviews, and other text content.en
placeIdYesGoogle Places ID of the restaurant

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.1/5.0
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the tool retrieves information, implying a read-only operation, but lacks details on permissions, rate limits, error handling, or response format. This is a significant gap for a tool with no annotation coverage.

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, efficient sentence that front-loads the purpose and lists key details without unnecessary words. Every element (verb, resource, information types) earns its place, making it appropriately sized and well-structured.

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?

Given the tool's moderate complexity (2 parameters, no output schema, no annotations), the description is minimally adequate. It covers the purpose and data types but lacks behavioral context, usage guidelines, and output details, leaving gaps that reduce completeness.

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 description coverage is 100%, so the schema fully documents both parameters (placeId and locale). The description does not add any parameter-specific details beyond what the schema provides, such as examples or usage context, resulting in a baseline score of 3.

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 clearly states the action ('Get detailed information') and resource ('about a specific restaurant'), specifying what information is retrieved (reviews, photos, opening hours). However, it does not explicitly differentiate from sibling tools like 'search_restaurants' or 'check_availability', which prevents a perfect score.

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?

The description provides no guidance on when to use this tool versus alternatives. It does not mention prerequisites (e.g., needing a placeId from search results), exclusions, or comparisons to siblings like 'search_restaurants' for finding restaurants or 'check_availability' for availability details.

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

Related Tools