Skip to main content
Glama
panoskiriakopoulos-sys

Rizerve MCP Server

Block or Unblock a Date

rizerve_block_date
Idempotent

Block or unblock a property date to mark it as unavailable for maintenance, owner stays, or manual blocks.

Instructions

Block or unblock a specific date for a property.

Use to mark dates as unavailable for maintenance, owner stays, or manual blocks.

Args:

  • slug (string): Property public slug

  • date (string): Date to block/unblock YYYY-MM-DD (required)

  • available (boolean): false to block, true to unblock (required)

  • reason (string): Optional reason (e.g. "maintenance", "owner_stay")

  • response_format ('markdown' | 'json'): Output format (default: 'markdown')

Examples:

  • "Block July 3rd for maintenance" → rizerve_block_date({ slug: "beachfront-villa", date: "2026-07-03", available: false, reason: "maintenance" })

  • "Unblock July 3rd" → rizerve_block_date({ slug: "beachfront-villa", date: "2026-07-03", available: true })

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dateYesDate to block or unblock (YYYY-MM-DD)
slugYesProperty public slug (e.g. "beachfront-villa")
reasonNoReason for blocking (e.g. "maintenance", "owner_stay")
availableYesSet to false to block, true to unblock
response_formatNoOutput format: 'markdown' for human-readable or 'json' for machine-readablemarkdown
Behavior4/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, and idempotentHint=true, so the description is not required to repeat this. It adds context about the toggle behavior and optional reason field, which is sufficient.

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?

The description is concise and well-structured, with a clear title, usage sentence, parameter list, and two illustrative examples. Every sentence earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 5-parameter tool with no output schema, the description adequately covers purpose, parameters, and usage examples. It could optionally explain default response format behavior, but the response_format parameter covers that.

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 baseline is 3. The description restates parameters and adds examples, but does not provide significant new meaning beyond the schema's built-in descriptions.

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?

The description clearly states the tool blocks or unblocks a specific date, with explicit use cases like maintenance, owner stays, or manual blocks. It distinguishes from siblings such as rizerve_batch_set_availability (batch) and rizerve_get_availability (read-only).

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?

The description explains when to use the tool (mark dates unavailable) but does not explicitly state when not to use it or compare to siblings like rizerve_batch_set_availability for bulk operations. However, examples provide practical context.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/panoskiriakopoulos-sys/rizerve-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server