Skip to main content
Glama

create_leave_type

Set up a new leave type by configuring its name, deduction behavior, approval requirement, calendar visibility, and optional hour or day limits.

Instructions

Create a new leave type (admins only).

Args: name: Name of the leave type (1–50 chars). deducted: Whether it deducts from the user's allowance. requires_approval: Whether bookings need approval. include_max_off: Whether it counts toward max-absent limits. is_private: Whether the leave type is private. color: A hex colour (see list_leave_type_colors). icon: An icon name (see list_leave_type_icons). calendar_visibility: Busy, Available or OutOfOffice. limit_hours: Optional limit in hours. limit_days: Optional limit in days.

Returns the ID of the new leave type.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
iconNo
nameYes
colorNo
deductedNo
is_privateNo
limit_daysNo
limit_hoursNo
include_max_offNo
requires_approvalNo
calendar_visibilityNo
Behavior4/5

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

No annotations are provided, so the description carries the full burden. It discloses that the tool creates a new leave type and returns its ID, but does not mention side effects, rate limits, or error conditions. It does not contradict any annotations.

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 an initial purpose statement followed by a clear list of parameters. Every sentence adds value, and there is no extraneous information.

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?

Given the tool's complexity (10 parameters, no output schema, no annotations), the description provides thorough parameter documentation and a return value. It could be more complete by mentioning potential errors or prerequisites, but overall it adequately covers the tool's behavior.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, yet the description adds detailed meaning for all 10 parameters. It explains each parameter's purpose, includes enumerated values for calendar_visibility, and directs users to sibling tools for color and icon options, exceeding compensation requirements.

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 'Create a new leave type' with a specific verb and resource. It explicitly says 'admins only' and distinguishes from sibling tools like update_leave_type and delete_leave_type.

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 specifies that it's for admins and references sibling tools for valid parameter values (list_leave_type_colors, list_leave_type_icons). However, it does not explicitly state when to use this tool versus alternatives like update_leave_type.

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/mlequime/timetastic-mcp'

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