Dubai Table

Request a table

request_table

Place a real table request with Dubai Table. Records the request, returns a booking reference (there is no booking fee and no payment link) and alerts the guest's relationship manager, who confirms with the venue on WhatsApp. Requires the guest's name and mobile number with country code. Accepts an exact table_id, a zone, or neither (the relationship manager places the party).

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": {
      "venue": "<venue>",
      "date": "<date>",
      "party": "<party>",
      "name": "<name>",
      "phone": "<phone>"
    },
    "name": "request_table"
  }
}

Input Schema

Name	Required	Description
`date`	Yes	YYYY-MM-DD
`name`	Yes	Guest name for the booking
`time`	No	Arrival time, e.g. 21:00
`zone`	No	Preferred zone if no table_id
`email`	No
`notes`	No
`party`	Yes
`phone`	Yes	Guest mobile with country code, e.g. +971501234567
`venue`	Yes
`source`	No	Which agent/app is booking, e.g. "chatgpt", "claude", "concierge-x"
`currency`	No	Kept for compatibility. There is no booking fee.
`occasion`	No	birthday, anniversary, business, celebration…
`table_id`	No	Exact table id as listed in table availability
`whatsappConsent`	No	True only if the guest explicitly agrees to WhatsApp booking updates from Dubai Table.

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 24, 2026

changedInput schema / properties / currency / description

Previous value: -"Kept for compatibility. The platform service fee is always charged in AED: AED 49.50."New value: +"Kept for compatibility. There is no booking fee."

Changed1 schema field changedOct 17, 2026

changedInput schema / properties / table_id / description

Previous value: -"Exact table from check_availability"New value: +"Exact table id as listed in table availability"

First observedOct 16, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Goes well beyond the annotations by disclosing that there is no booking fee or payment link, that a relationship manager confirms with the venue over WhatsApp (a human-in-the-loop step), and that a booking reference is returned. It does not state what happens on failure or that repeated calls create duplicate requests, which is the main remaining behavioral gap.

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?

Four tight sentences, front-loaded with what the tool does and what it returns, then prerequisites, then the location-selection branching. No filler and nothing redundant with the schema.

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?

For a 14-parameter mutation tool this covers the essentials: outcome, no-fee/no-payment behavior, human confirmation path, and required guest identity fields. With an output schema present, return-value detail is rightly omitted; a note on duplicate-request behavior would make it complete.

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?

Schema coverage is 71%, and the description fills a meaningful gap by explaining the table_id / zone / neither interaction — that omitting both means the relationship manager chooses the party's table. It also reinforces the country-code requirement on phone. It does not cover whatsappConsent or source, so it is not exhaustive.

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 verb and resource ('Place a real table request with Dubai Table') and immediately clarifies the outcome: a recorded request plus a booking reference. This is clearly distinguishable from read-only siblings like check_availability and show_tables.

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 closing sentence gives real branching guidance ('Accepts an exact table_id, a zone, or neither'), and the phone/name requirement is stated. But it never says when to prefer this over check_availability or show_tables, nor that booking_status should be used to follow up — the agent must infer the workflow position.

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

All Dubai Table tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?