Skip to main content
Glama
Sign In
Restaurant Booking MCP Server

Restaurant Booking MCP Server

by samwang0723
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get_booking_instructions

Obtain step-by-step instructions for making a reservation at a specific restaurant using the Google Places ID, available in multiple locales for user convenience.

Instructions

Get instructions on how to make a reservation at a specific restaurant

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_booking_instructions"
  }
}

Input Schema

NameRequiredDescriptionDefault
localeNoLocale for booking instructions (e.g., "en", "zh-TW", "ja", "ko")en
placeIdYesGoogle Places ID of the restaurant

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/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 instructions but doesn't cover critical aspects like whether it's a read-only operation, potential rate limits, authentication needs, or what the return format looks like (e.g., text, structured data). This leaves significant gaps for an agent to use it effectively.

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 directly states the tool's purpose without unnecessary words. It's front-loaded with the core action ('Get instructions'), making it easy to parse and understand quickly.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the lack of annotations and output schema, the description is incomplete for effective tool use. It doesn't address behavioral traits (e.g., safety, performance) or output details, which are crucial for an agent to handle this tool correctly in a broader context with sibling tools like 'make_reservation'.

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?

The input schema has 100% description coverage, clearly documenting both parameters ('locale' and 'placeId') with their purposes and types. The description doesn't add any semantic details beyond what the schema provides, such as explaining how 'placeId' relates to restaurant selection or the impact of 'locale' on instruction content. Baseline 3 is appropriate since the schema does the heavy lifting.

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 tool's purpose with a specific verb ('Get') and resource ('instructions on how to make a reservation at a specific restaurant'), making it immediately understandable. However, it doesn't explicitly differentiate from sibling tools like 'check_availability' or 'make_reservation', which might involve related reservation processes.

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 such as 'check_availability' or 'make_reservation'. It lacks context about prerequisites (e.g., needing a restaurant ID) or exclusions, leaving the agent to infer usage based on the tool name alone.

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