Pagosa Forest Lodge

get_booking_link

Read-onlyIdempotent

Revalidate a quote and return the official Lodgify checkout URL when verified. The guest reviews terms and completes checkout; no reservation is created.

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": {
      "checkIn": "<checkIn>",
      "checkOut": "<checkOut>",
      "adults": "<adults>",
      "children": "<children>",
      "infants": "<infants>",
      "pets": "<pets>",
      "quoteId": "<quoteId>"
    },
    "name": "get_booking_link"
  }
}

Input Schema

Name	Required	Description
`pets`	Yes	Up to two dogs require prior approval. Lodgify lists a USD 100 fixed pet add-on per stay; the live quote controls the applied amount and taxes.
`adults`	Yes
`checkIn`	Yes	Arrival date in America/Denver property-local calendar time.
`infants`	Yes
`quoteId`	Yes
`checkOut`	Yes	Departure date, exclusive, in America/Denver property-local calendar time.
`children`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 14, 2026

TDQS

B3.3/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description's 'no reservation is created' reinforces that side-effect boundary and 'when verified' hints that the call can fail, but it says nothing about auth requirements, failure modes, or URL lifetime.

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 tight sentences, front-loaded with the action and result, with the guest-workflow and no-reservation caveat as the follow-up. No filler and nothing redundant.

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?

With no output schema, the description usefully states the return artifact (the checkout URL), but it leaves the low-coverage parameter set and error behavior undocumented. Adequate for the core action, incomplete for a seven-required-parameter tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Seven required parameters with only 43% schema description coverage, and the description mentions none of them. quoteId, adults, children and infants are undocumented in both places, so the description fails to compensate for the coverage gap; only the loose mention of 'a quote' touches quoteId.

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 sequence (revalidate a quote, return the checkout URL) and a precise resource (official Lodgify checkout URL). It is clearly separable from get_quote or check_availability, though it never names a sibling to make the boundary explicit.

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?

Implies the moment of use — a guest ready to review terms and complete checkout — and hints at a verification precondition ('when verified'). It gives no explicit when-not-to-use rule and never points at get_quote for the earlier quoting step, so routing is only implied.

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

All Pagosa Forest Lodge 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?