Skip to main content
Glama
mikkmihkel

BambooHR MCP Server

by mikkmihkel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Vacation overview

bamboohr_vacation_overview
Read-onlyIdempotent

Get a company-wide vacation report for any calendar year, showing balances, used time, planned and unplanned days, and longest continuous blocks. Filter to employees missing a 14-day vacation block to identify coverage risks.

Instructions

Company-wide vacation report for one calendar year. For every current employee: vacation balance as of a date, used year-to-date, vacation planned after that date (approved or requested), unplanned balance (balance minus planned), the longest continuous vacation block in calendar days, and whether they have at least one 14-day continuous block. Adjacent requests are merged into one block. Use onlyMissingFourteenDayBlock to list only employees who have not taken or booked a 14-day vacation. The summary counts all employees before the onlyMissingFourteenDayBlock filter is applied. Note: planned vacation excludes a request already in progress on the as-of date, on the assumption that BambooHR's balance has already deducted it.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
asOfNoBalance date, YYYY-MM-DD, must be inside the year. Default: today (or Dec 31 for past years).
yearNoCalendar year. Default: current year.
departmentNoOnly employees in this department (exact name, case-insensitive).
timeOffTypeNoVacation time-off type name or id. Default: BAMBOOHR_VACATION_TYPE, else a type named like 'vacation' or 'puhkus'.
onlyMissingFourteenDayBlockNoReturn only employees without a 14-day continuous block.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv3.0.0

TDQS

A4.6/5.0
Behavior5/5

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

The description goes far beyond the readOnlyHint/idempotentHint annotations by disclosing important behaviors: adjacent requests are merged, the summary counts before the onlyMissingFourteenDayBlock filter, and planned vacation excludes a request already in progress because BambooHR's balance may have already deducted it. This is exactly the kind of non-obvious behavior an agent needs.

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 dense but every sentence carries information: the report scope, the detailed output fields, the block-merging rule, the filter behavior, and the critical caveat about in-progress requests. It is front-loaded with the most important scoping statement.

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?

With no output schema, the description compensates by enumerating all returned columns and their meanings. It could additionally clarify what 'current employee' means or whether results are paginated, but for the tool's complexity the essential calling context is present.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3. The description adds real value by explaining the interaction of onlyMissingFourteenDayBlock with the summary count, the as-of date semantics, and default timeOffType resolution, which are not evident from the schema alone.

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 states a specific purpose: a company-wide vacation report for one calendar year, and enumerates the exact computed columns (balance, used YTD, planned, unplanned, longest block, 14-day block flag). This clearly distinguishes it from individual-level sibling tools like bamboohr_time_off_balances or bamboohr_time_off_requests.

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 phrase 'Company-wide vacation report' and 'For every current employee' provides clear context that this is an aggregate overview, not a per-employee lookup. However, it does not explicitly name alternatives or state when not to use it, so it stops short of full exclusion guidance.

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

Deploy Server

Other Tools