Pagosa Forest Lodge

check_availability

Read-onlyIdempotent

Check authoritative availability for the requested stay. Provider outages return provider_unavailable, never stay_unavailable.

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>"
    },
    "name": "check_availability"
  }
}

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
`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.4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds genuinely new behavioral information about failure semantics: provider outages surface as provider_unavailable and never as stay_unavailable, which tells the agent how to interpret a negative result.

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 with no filler; the core purpose is front-loaded and the error-semantics nuance follows. Every sentence earns its place.

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, idempotent tool with annotations covering the safety profile and no output schema, the description is nearly complete, covering purpose and the key provider_unavailable outcome. Minor gaps remain around the meaning of the three undocumented guest-count parameters.

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?

Schema description coverage is only 50% (pets, checkIn, checkOut documented; adults, children, infants bare). The description adds nothing about parameter meaning, formats, or constraints, so it fails to compensate for the undocumented half.

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 a specific verb and resource ('Check authoritative availability') and qualifies the scope with 'for the requested stay', which an agent can distinguish from siblings like search_stays or get_quote. It does not, however, explicitly contrast itself with any sibling tool.

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

Usage Guidelines2/5

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

There is no statement of when to reach for this tool versus search_stays, get_quote, or get_property, nor any preconditions (e.g. that a stay must first be selected). 'For the requested stay' implies a context but gives no routing guidance.

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?