Skip to main content
Glama

Guest2Host

Get stay details

get_stay
Read-onlyIdempotent

Full details for one stay: description, amenities, beds and baths, photos, approximate location, host name, owner-reported ratings, links to the same home on Airbnb/Vrbo when the owner lists them, and when its calendar last synced.

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

Input Schema

NameRequiredDescriptionDefault
slugYesThe stay's slug, from search_stays

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already establish that this is a read-only, idempotent, non-destructive, non-open-world operation. The description adds useful disclosure of what is returned, including owner-reported ratings, cross-platform links, and calendar sync recency. It does not cover error behavior for missing or invalid slugs, so it adds context but not full behavioral detail.

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?

The description is a single front-loaded sentence that begins with the core purpose and then enumerates returned fields efficiently. The field list is long but each item adds useful information about the response.

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 simple one-parameter read operation with no output schema, the description is largely complete: it explains the scope and enumerates the returned fields. Minor gaps remain around invalid-slug behavior and any limits, but these are small for a read-only detail tool.

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%, and the sole parameter is already documented as the stay slug from search_stays. The description does not add syntax, format, or source guidance beyond what the schema provides, so the baseline 3 is appropriate.

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 states a specific resource and scope: full details for exactly one stay, with an enumerated field list. It distinguishes itself from search_stays by pointing to the slug source, though it does not explicitly name alternatives.

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 phrase "slug, from search_stays" implies this is a follow-up lookup after a search, giving useful implied usage. However, there is no explicit guidance on when not to use it or how it differs behaviorally from other detail-oriented siblings.

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