Threshold

Get a binding price

get_quote

Read-onlyIdempotent

Itemized, binding price for exact dates and party, after re-checking the host's live calendars. Valid 10 minutes. Returns house rules and an exact refund schedule to show the guest. Does not reserve the dates. Maps to POST /v1/properties/{id}/quotes.

Input Schema

TableJSON Schema

Name	Required	Description
`pets`	No	Number of pets. Default 0. Service animals don't count.
`adults`	Yes	Number of adults (at least 1).
`infants`	No	Number of infants under 2. Default 0.
`check_in`	Yes	Arrival date, YYYY-MM-DD.
`children`	No	Number of children aged 2 to 12. Default 0.
`check_out`	Yes	Departure date, YYYY-MM-DD.
`property_id`	Yes	The property's id, from search_stays.

Output Schema

TableJSON Schema

Name	Required	Description
`id`	No
`total`	No	An amount in cents with its currency.
`nights`	No
`payment`	No
`check_in`	No
`check_out`	No
`expires_at`	No
`line_items`	No
`house_rules`	No
`property_id`	No
`booking_mode`	No
`refund_schedule`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed8 schema fields changedOct 14, 2026

addedInput schema / properties / adults / description
```
Added value: +"Number of adults (at least 1)."
```
addedInput schema / properties / check_in / description
```
Added value: +"Arrival date, YYYY-MM-DD."
```
addedInput schema / properties / check_out / description
```
Added value: +"Departure date, YYYY-MM-DD."
```

addedInput schema / properties / children / description

Added value: +"Number of children aged 2 to 12. Default 0."

addedInput schema / properties / infants / description

Added value: +"Number of infants under 2. Default 0."

addedInput schema / properties / pets / description

Added value: +"Number of pets. Default 0. Service animals don't count."

addedInput schema / properties / property_id / description
```
Added value: +"The property's id, from search_stays."
```

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "description": "A binding price for the stay, valid until expires_at.",
+  "properties": {
+    "booking_mode": {
+      "type": "string"
+    },
+    "check_in": {
+      "type": "string"
+    },
+    "check_out": {
+      "type": "string"
+    },
+    "expires_at": {
+      "type": "string"
+    },
+    "house_rules": {
+      "type": "array"
+    },
+    "id": {
+      "type": "string"
+    },
+    "line_items": {
+      "type": "array"
+    },
+    "nights": {
+      "type": "integer"
+    },
+    "payment": {
+      "type": "object"
+    },
+    "property_id": {
+      "type": "string"
+    },
+    "refund_schedule": {
+      "type": "array"
+    },
+    "total": {
+      "description": "An amount in cents with its currency.",
+      "properties": {
+        "amount": {
+          "type": "integer"
+        },
+        "currency": {
+          "type": "string"
+        }
+      },
+      "type": "object"
+    }
+  },
+  "type": "object"
+}

First observedOct 2, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Beyond the readOnly/idempotent/non-destructive annotations, the description adds genuinely useful traits: a 10-minute validity window, that it returns house rules and a refund schedule, and that it does not hold the dates. These are the facts an agent needs before quoting a guest. It does not mention rate limits or what happens if the calendar re-check fails.

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?

Four short sentences, each carrying distinct information, with the core purpose front-loaded. The trailing API mapping is compact and does not crowd out the important behavioral facts.

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?

For a read-only quote tool with an output schema already present, the description covers purpose, freshness, validity window, what is returned, and the crucial non-reservation caveat. Nothing an agent needs to call it or set guest expectations is missing.

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 description coverage is 100%, so every parameter (property_id, dates, adults, children, infants, pets) is already documented in the schema. The description adds only the high-level notion of 'party' and 'exact dates' without new parameter-level meaning, so the 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?

States a specific verb and resource ('Itemized, binding price') with the exact scoping ('for exact dates and party'), which cleanly separates it from check_availability (availability only) and request_booking (which reserves). An agent can route correctly without opening the schema.

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

Usage Guidelines4/5

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

Gives clear context: it re-checks the host's live calendars, so it is the pricing step after availability, and 'Does not reserve the dates' implies the follow-up is a booking request. It stops short of naming request_booking as the alternative, so the when-to-use guidance is strong but not fully explicit.

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

All Threshold 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?