Pagosa Forest Lodge

get_quote

Read-onlyIdempotent

Request a complete current quote in USD. Incomplete charges or terms fail closed. A quote does not hold inventory.

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": "get_quote"
  }
}

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

A3.5/5.0

Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive, so the bar is lower. The description still adds real value: quotes never hold inventory (no state change), and incomplete charges/terms fail closed rather than returning a partial quote. It omits quote validity/expiry and any rate considerations.

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?

Three short sentences with zero padding, and the core purpose is front-loaded ahead of the constraints. Every sentence carries distinct information.

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?

For a 6-required-parameter pricing call with no output schema, the description covers currency and failure semantics but not what a quote actually returns (line items, taxes, expiry) or the parameters it leaves undocumented. Adequate but with clear gaps.

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% – adults, children, and infants have no description anywhere. The description adds nothing about any parameter (no date semantics, no occupancy rules, no pet handling), so it does not compensate for the documented gaps.

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 and resource ('Request a complete current quote'), adds the currency (USD) and two scoping facts. The statement 'A quote does not hold inventory' implicitly separates it from booking-type siblings, though no sibling is named explicitly.

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 only implied – an agent can infer this is the pricing step before booking, but the description never says when to call it versus check_availability or get_booking_link. 'Fail closed' hints at behavior on bad input rather than 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?