Threshold

Get property details

get_property

Read-only

Full record for one property: beds by room, amenities with details, access and stairs, rules, host FAQ, policies, and verification status. The location is approximate on purpose: the exact address and the host's direct contact details are not in the record and are sent to the guest after a confirmed booking, so if asked, say that rather than that they are missing. Maps to GET /v1/properties/{id}.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`property_id`	Yes	The property's id, from search_stays (starts with prop_).

Output Schema

TableJSON Schema

Name	Required	Description	Default
`id`	No
`faq`	No
`rules`	No
`listing`	No
`capacity`	No
`location`	No
`policies`	No
`amenities`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 14, 2026

addedInput schema / properties / property_id / description

Added value: +"The property's id, from search_stays (starts with prop_)."

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "description": "Everything public about one place: description, rooms and beds, amenities, access, rules, policies, photos and the host's answers to common questions.",
+  "properties": {
+    "amenities": {
+      "type": "array"
+    },
+    "capacity": {
+      "type": "object"
+    },
+    "faq": {
+      "type": "array"
+    },
+    "id": {
+      "type": "string"
+    },
+    "listing": {
+      "type": "object"
+    },
+    "location": {
+      "type": "object"
+    },
+    "policies": {
+      "type": "object"
+    },
+    "rules": {
+      "type": "object"
+    }
+  },
+  "type": "object"
+}

First observedOct 2, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Beyond the readOnly/non-destructive annotations, it discloses a non-obvious data limitation — the location is deliberately approximate and the exact address plus host direct contact are withheld until a confirmed booking — and prescribes the correct phrasing so the agent does not report them as missing. That is exactly the kind of behavioral context annotations cannot convey.

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?

Front-loads the payload contents, then the important address caveat, then the endpoint mapping. The enumerated content list is slightly long but each clause maps to real record sections, and no sentence is filler.

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?

With an output schema present the return shape need not be restated, and the description covers scope, the data-gap gotcha, and the underlying endpoint for a single-parameter read tool. Nothing an agent needs to call this correctly 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?

There is one parameter with 100% schema description coverage, and the schema already says the id comes from search_stays and starts with prop_. The description adds nothing about the parameter, so the baseline 3 for high coverage 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 ('Full record for one property') and enumerates what the record contains (beds by room, amenities, access/stairs, rules, policies, verification status), which clearly separates it from search_stays and the booking/messaging siblings. The mapping to GET /v1/properties/{id} removes any remaining ambiguity.

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?

Usage context is clear: it is the single-property detail fetch whose id comes from search_stays, and it adds an explicit instruction for how to answer when the exact address is requested. It does not name a when-not condition or a competing sibling, but none of the listed siblings is a real alternative for this lookup.

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?