Skip to main content
Glama

create-timeoff

Submit a time off request for one or more employees by providing their IDs, date range, and time off type. Optionally include hours, notes, and status.

Instructions

Create a new time off request

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
people_idsYesArray of person IDs (people_ids) - Float API expects plural field
timeoff_type_idYesThe time off type ID
start_dateYesStart date (YYYY-MM-DD)
end_dateYesEnd date (YYYY-MM-DD)
hoursNoHours of time off (omit for full day)
full_dayNo1 for full day, 0 for partial day
notesNoOptional notes
statusNoStatus (1 for pending, 2 for approved, 3 for rejected - Float API uses numeric status codes)
repeat_stateNoRepeat configuration
repeat_endNoEnd date for repeating time off (YYYY-MM-DD)
Behavior2/5

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

Only states the verb 'create' without disclosing side effects, permissions, or notification behaviors. No annotations are provided, so the description bears full burden, and it fails to convey key behavioral traits.

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, clear sentence that efficiently states the tool's purpose with no redundant information.

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?

Given 10 parameters and no output schema, the description is minimal but sufficient for a straightforward create operation. It does not explain return values or success confirmation, which would improve completeness.

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?

Input schema has 100% coverage with clear descriptions for all 10 parameters. The description adds no extra semantic value beyond the schema, but baseline is adequate.

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?

Description clearly states the tool creates a new time off request, distinguishing it from siblings like approve-timeoff or update-timeoff. However, it lacks specificity about the scope (single vs. bulk) and could more explicitly contrast with bulk-create-timeoff.

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

Usage Guidelines2/5

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

No guidance on when to use this tool versus alternatives. Siblings like approve-timeoff or bulk-create-timeoff are not mentioned, leaving the agent to infer usage 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/asachs01/float-mcp'

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