Skip to main content
Glama

Guest2Host

Get booking link

get_booking_link
Read-onlyIdempotent

The link to book a stay on the owner's own website, where the guest books and pays the owner directly. Guest2Host takes no fee and never handles payment. Optional dates and guests are passed along for reference.

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": {
      "slug": "<slug>"
    },
    "name": "get_booking_link"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYesThe stay's slug, from search_stays
guestsNo
checkInNoCheck-in date, YYYY-MM-DD
checkOutNoCheck-out date, YYYY-MM-DD

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the description is not required to restate safety. It still adds real context: Guest2Host takes no fee and never handles payment, and the optional dates/guests are only 'passed along for reference' — telling the agent these inputs do not hold or reserve anything.

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?

Two sentences with no filler, and the core behavior (who books and pays, no fee) is front-loaded before the secondary note about optional parameters.

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 read-only, non-destructive link retrieval with one required and three optional parameters and no output schema, the description covers purpose, payment flow, and the role of optional inputs. It does not say whether links expire, what happens when requested dates are unavailable, or what fields the link response carries, which are minor but real gaps.

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 75%, and slug is explicitly traced back to search_stays. The description goes beyond the schema by characterizing checkIn, checkOut, and guests as optional reference-only data rather than booking-binding inputs, which is meaning the schema's patterns and bounds do not convey.

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 names the specific resource and its purpose: a link to book a stay on the owner's own website, where the guest books and pays the owner directly. That is concrete enough to distinguish it from mutation-oriented siblings like apply_to_list or send_inquiry, but it never explicitly contrasts itself with get_stay or check_dates.

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?

Usage is implied: reach for this when a guest should complete a booking off-platform and pay the owner directly, with no fee to Guest2Host. There is no explicit when-not or named alternative such as get_stay for details or check_dates for availability, so the agent must infer the routing.

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