Threshold

Check a property's calendar

check_availability

Read-only

Day-by-day availability and indicative nightly prices for up to 180 days. Cached; use get_quote to confirm. Useful when the guest's dates are flexible. Maps to GET /v1/properties/{id}/availability.

Input Schema

TableJSON Schema

Name	Required	Description
`to`	Yes	Exclusive
`from`	Yes	First night to check, YYYY-MM-DD.
`property_id`	Yes	The property's id, from search_stays.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`days`	No
`timezone`	No
`property_id`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedOct 14, 2026

addedInput schema / properties / from / description

Added value: +"First night to check, YYYY-MM-DD."

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": "Night-by-night availability.",
+  "properties": {
+    "days": {
+      "items": {
+        "additionalProperties": true,
+        "description": "One night.",
+        "properties": {
+          "available": {
+            "type": "boolean"
+          },
+          "date": {
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "property_id": {
+      "type": "string"
+    },
+    "timezone": {
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

First observedOct 2, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnly, non-destructive, closed-world), and the description adds genuinely new behavior: results are cached, prices are indicative rather than binding, and there is a 180-day ceiling. That cached/stale caveat is exactly the kind of operational detail annotations cannot express.

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, zero filler. Return content is front-loaded, followed by the usage trigger, the confirmation caveat, and the endpoint mapping last.

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?

An output schema exists, so return values need no explanation. Between the annotations, the 100%-covered schema, the caching/indicative-price caveat and the get_quote pointer, an agent has everything needed to call this correctly for a flexible-date search.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, but the description adds a real parameter constraint not present in the schema: the from/to window cannot exceed 180 days. The schemas own notes (from = first night, to = exclusive) remain the source of truth for semantics.

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 the resource (day-by-day availability plus indicative nightly prices) and scopes it precisely to 180 days, so an agent knows exactly what comes back. It partially differentiates from siblings by pointing at get_quote, but does not clarify its relationship to get_property or search_stays, which also touch the same property entity.

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?

'Useful when the guest's dates are flexible' gives a clear positive trigger, and 'use get_quote to confirm' routes the agent to the alternative for firm pricing. It stops short of an explicit when-not (e.g. 'do not use this for a confirmed booking price'), so 4 rather than 5.

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?