NuVista Haven MCP Server

Get Quote

get_quote

Quote a stay: nightly rate x nights + cleaning fee.

Nightly rates are live from Hospitable. If the cleaning fee is not exposed by the API, the total is marked as a partial estimate.

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": {
      "property": "<property>",
      "check_in": "<check_in>",
      "check_out": "<check_out>"
    },
    "name": "get_quote"
  }
}

Input Schema

Name	Required	Description	Default
`guests`	No
`check_in`	Yes
`property`	Yes
`check_out`	Yes

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 15, 2026

TDQS

B3/5.0

Behavior3/5

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

With no annotations, the description carries the full burden, and it does add real behavioral context: rates are live from Hospitable and the total is flagged as a 'partial estimate' when the cleaning fee is unavailable. That is genuinely useful edge-case disclosure. However, it says nothing about auth requirements, whether the quote is guaranteed or time-limited, or any rate limits.

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?

Three short sentences, front-loaded with the pricing formula, with no filler. Every sentence carries information, though the middle 'rates are live from Hospitable' line is terse enough to read as vendor trivia rather than agent-relevant guidance.

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?

An output schema exists, so return-value detail is not required. The description covers the computation and the partial-estimate edge case, but with no annotations and 0% parameter coverage it leaves an agent guessing about input formats and whether the quote implies a booking hold.

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 0% across 4 parameters, so the description must compensate and largely does not. 'Nights' implies check_in/check_out are dates, but the description never explains the date format, whether 'property' is an ID or name, or what 'guests' affects (e.g. pricing tiers or capacity limits).

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 (quote) and resource (a stay), and even gives the computation model ('nightly rate x nights + cleaning fee'), so the agent knows exactly what comes back. It does not, however, explicitly contrast itself with siblings like check_availability or get_property_details, so a 5 is not warranted.

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 use this tool versus check_availability, get_booking_link, or get_property_details, and no prerequisites are given. Usage is only inferable from the verb 'Quote a stay'; nothing is said about required inputs or when a quote is inappropriate (e.g. unverified availability).

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

All NuVista Haven MCP Server 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?