Skip to main content
Glama

White Sands Residences

Create Lodgify booking link

get_booking_link

Creates the existing Lodgify checkout URL prefilled with arrival date, departure date and number of guests. Use after checking availability and calculating the price.

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": {
      "arrival": "<arrival>",
      "departure": "<departure>",
      "guests": "<guests>"
    },
    "name": "get_booking_link"
  }
}

Input Schema

NameRequiredDescriptionDefault
guestsYesNumber of guests, between 2 and 10.
arrivalYesArrival date in YYYY-MM-DD format.
departureYesDeparture date in YYYY-MM-DD format.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full disclosure burden. Saying the output is a prefilled checkout URL usefully signals this is a link-generation step rather than a reservation, but it never states whether the link holds inventory, whether it expires, whether the call is idempotent, or what permissions are needed. For an unannotated tool those are meaningful gaps an agent would want covered.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences, with the output artifact stated first and the sequencing guidance second, so nothing is buried. Minor waste in the awkward "creates the existing" phrasing, but overall tight.

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 three-parameter tool with no output schema, the description should say something about the returned value, such as whether it is a URL string or a structured object and whether it has a lifetime. It covers the input side and the ordering well but leaves the return contract entirely unaddressed.

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%, with each of the three parameters documented including format and the 2-10 guest range, so the baseline is 3. The description merely restates the same three inputs and adds no constraint or interpretation beyond the schema.

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?

States a specific verb and resource: produces a Lodgify checkout URL prefilled with arrival, departure, and guests. It is distinguishable from the pricing and availability siblings by naming the artifact it returns. The phrase "creates the existing ... URL" is slightly self-contradictory in wording and the tool name uses "get" while the description says "Creates," which adds minor friction.

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?

"Use after checking availability and calculating the price" gives an explicit ordering relative to the check_availability and get_price_quote siblings, which is genuinely actionable. It stops short of stating when not to use it or what to do if availability has not been confirmed, so it falls short of a 5.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources