Headed In: Florida trips, water and weather

Rental guest guidebook

stay_guidebook

Read-onlyIdempotent

A short-term rental's guest guidebook (any U.S. house), from the link or code on the house's fridge card (headedin.com/stay/): the host's welcome, house notes (Wi-Fi name, check-out, parking, trash, beach gear), house rules, the host's own local picks with map links, the listing link, and the house's approximate spot (for a Florida house, the other tools here use it for nearby beach, red tide and event info). Only pages the host has published, and only by their own link: it can't search or list rentals. No door codes or passwords are ever on a page. Use it when a guest shares their rental's guidebook link or asks what their host said about the house.

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": {
      "page": "<page>"
    },
    "name": "stay_guidebook"
  }
}

Input Schema

Name	Required	Description	Default
`page`	Yes	The guidebook link, e.g. https://headedin.com/stay/pelican-house-demo, or just the code after /stay/

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 11, 2026

TDQS

A4.4/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 open-world, so the safety profile is covered. The description adds genuinely new behavioral context: no door codes or passwords ever appear on a page, and unshared/unpublished guidebooks are unreachable. It stops short of describing failure behavior for a bad or unpublished code.

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 resource and input format are front-loaded, and the long content enumeration earns its place by letting an agent judge whether the guidebook answers the guest's question. The single opening sentence is heavy and could be split for scanability.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, so the description carries the burden of describing return content — and it does, field by field. With one fully documented parameter, the privacy caveat and the access restriction, an agent has everything needed to call this correctly.

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 single 'page' parameter already documents that either a full link or the code after /stay/ is accepted. The description restates that format with the fridge-card framing and the headedin.com/stay/<code> pattern, which helps recognition but adds no meaning the schema lacks. Baseline 3 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?

Names a specific resource (a short-term rental's guest guidebook) and enumerates exactly what it contains: welcome, house notes, rules, host picks with map links, listing link, approximate location. It also states the negative scope ('can't search or list rentals'), which separates it from any sibling that discovers places.

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

Usage Guidelines5/5

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

Explicit trigger is given: 'Use it when a guest shares their rental's guidebook link or asks what their host said about the house.' It also states the access precondition (only host-published pages, only via their own link) and hints that the returned location feeds the Florida-oriented sibling tools for beach, red tide and event lookups.

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

All Headed In: Florida trips, water and weather 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?