Skip to main content
Glama
Sign In
MCP Booking

MCP Booking

by markswendsen-code
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

booking_save_property

Save any property to your Booking.com favorites using its URL or property ID. Requires an active login session.

Instructions

Save a property to your Booking.com wishlist/favorites. Requires being logged in.

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": {
      "propertyUrl": "<propertyUrl>"
    },
    "name": "booking_save_property"
  }
}

Input Schema

NameRequiredDescriptionDefault
propertyUrlYesFull property URL or propertyId from search results

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.1

TDQS

A3.7/5.0
Behavior2/5

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

No annotations are provided, so the description bears full responsibility. It only mentions the login requirement but does not disclose other behaviors (e.g., idempotency, what happens if already saved, side effects, or response format).

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 sentence with no extraneous words. It is front-loaded and efficiently conveys the core purpose and a key prerequisite.

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 simplicity (1 parameter, no output schema), the description is minimally adequate. It states purpose and a condition but lacks details on return values or verification of success. Could be improved by noting what the tool returns or confirms.

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 schema already describes the parameter ('Full property URL or propertyId from search results'). The description does not add additional meaning beyond what the schema provides, so baseline score applies.

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 action ('Save') and the target resource ('property to your Booking.com wishlist/favorites'). This distinguishes it from siblings like 'booking_book' (books) and 'booking_get_property' (retrieves info).

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

Usage Guidelines4/5

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

Specifies a necessary condition ('Requires being logged in'), which aids in tool selection. However, it lacks explicit guidance on when not to use this tool or alternatives like 'booking_book' or 'booking_get_property'.

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