Caly

Add time off

create_out_of_office

Block a date range as out of office; bookings in that range are prevented and optionally redirected to a teammate.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "startDate": "<startDate>",
      "endDate": "<endDate>",
      "reasonId": "<reasonId>"
    },
    "name": "create_out_of_office"
  }
}

Input Schema

Name	Required	Description
`notes`	No
`endDate`	Yes	Date (YYYY-MM-DD) or ISO 8601 datetime.
`reasonId`	Yes	From list_ooo_reasons.
`startDate`	Yes	Date (YYYY-MM-DD) or ISO 8601 datetime.
`toTeamUserId`	No	Team member who takes bookings while away (userId from list_members), or null.
`showNotePublicly`	No

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 30, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already declare this is a non-read-only, non-destructive, non-idempotent open-world mutation. The description adds useful operational context beyond them: the block prevents bookings in the range and can redirect them to a teammate. It does not mention permissions, duplicate-handling, or what happens to existing bookings at creation time.

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?

A single well-formed sentence that front-loads the main action and appends the booking impact. No filler sentences.

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

Completeness3/5

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

For a 6-parameter mutation with no output schema, the description conveys the core effect but omits important caller-relevant details: reasonId must be fetched from list_ooo_reasons, whether overlapping OOO ranges are rejected, and the visibility behavior of showNotePublicly/notes.

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 coverage is 67%. The description covers the date range and the optional teammate redirect, but does not mention the required reasonId (nor that it comes from list_ooo_reasons), nor the semantics of notes/showNotePublicly. It partially compensates but leaves required-parameter guidance to the schema.

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 states a specific verb and resource ('Block a date range as out of office') and explains the effect on bookings. It is clearly distinct from delete_out_of_office/update_out_of_office in intent, though it does not name any sibling explicitly.

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

Usage Guidelines3/5

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

Usage is implied: create an out-of-office block for a date range. There is no explicit guidance on when to use this versus update_out_of_office or list_out_of_office, nor any stated prerequisites such as needing a reason from list_ooo_reasons.

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

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