Fetch a Vrbo property's rate calendar by property ID to view availability, nightly prices, check-in/out rules, and stay constraints for planning bookings.
Get a Vrbo property rate calendar. Returns public calendar dates, nightly display prices when provided, availability, check-in/out validity, and stay constraints.
| Name | Required | Description | Default |
|---|---|---|---|
| property_id | Yes | Vrbo property ID (optionally ending in ha) |
Changes observed during successful MCP inspections.
v1.17.9Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full behavioral burden. It helpfully enumerates the returned data (calendar dates, nightly prices when provided, availability, check-in/out validity, stay constraints), but omits operational traits such as read-only safety, authentication needs, rate limits, or date-range coverage.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two sentences, front-loaded with the purpose and followed by return details. Every phrase contributes and there is no wasted wording.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple one-parameter read operation with no output schema, the description adequately explains what the tool returns. It could be more complete by clarifying date coverage or constraints on the calendar, but it is sufficient for correct invocation.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, with property_id fully documented in the input schema. The description adds no additional meaning about the parameter, so the baseline 3 is appropriate.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb ('Get') and resource ('Vrbo property rate calendar'), making the tool's function clear. It does not explicitly contrast with sibling tools such as vrbo_property or vrbo_properties_reviews, so it falls short of full sibling differentiation.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance is given on when to use this tool versus alternatives like vrbo_property or vrbo_search. Prerequisites and exclusions are absent, so usage must be inferred from the tool name alone.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.