Skip to main content
Glama
mikkmihkel

BambooHR MCP Server

by mikkmihkel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Vacation overview

bamboohr_vacation_overview
Read-onlyIdempotent

Get vacation report per department or employee list for a year: balance, used, planned, unplanned, longest block, and filter for missing 14-day blocks.

Instructions

Vacation report for one department (or a list of employeeIds) and one calendar year: 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. A department or employeeIds is required — a company-wide overview in one call is not allowed, ask per department — and the group must fit the per-call record limit. Use onlyMissingFourteenDayBlock to list only employees without a 14-day vacation. The summary counts all employees before that filter. 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).
employeeIdsNoOnly these employees. Use instead of, or together with, department.
timeOffTypeNoVacation time-off type name or id. Default: the enrolled 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. Changed5 schema fields changedv4.1.0
    • addedInput schema / properties / department / minLength
      Added value: +1
    • addedInput schema / properties / employeeIds
      Added value: +{
+  "description": "Only these employees. Use instead of, or together with, department.",
+  "items": {
+    "exclusiveMinimum": 0,
+    "type": "integer"
+  },
+  "type": "array"
+}
    • addedInput schema / properties / timeOffType / $ref
      Added value: +"#/properties/department"
    • changedInput schema / properties / timeOffType / description
      Previous value: -"Vacation time-off type name or id. Default: BAMBOOHR_VACATION_TYPE, else a type named like 'vacation' or 'puhkus'."New value: +"Vacation time-off type name or id. Default: the enrolled vacation type, else a type named like 'vacation' or 'puhkus'."
    • removedInput schema / properties / timeOffType / type
      Removed value: -"string"
  2. 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 annotations already cover readOnlyHint, openWorldHint, idempotentHint, and non-destructiveness, so the safety profile is clear. The description adds non-obvious calculation behaviors beyond annotations: adjacent requests are merged into one block, planned vacation excludes an in-progress request, and the summary counts all employees before the filter is applied.

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 well organized: report contents first, then invocation constraints, then filter behavior, then an edge-case note. Each sentence carries a distinct and necessary fact, with no filler or repetition of the tool name.

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 naming each computed field and explaining the in-progress request exclusion and per-call limits. The only minor gap is that the exact response envelope is not described, but an agent has enough information to invoke the tool correctly and interpret the returned concepts.

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, and each parameter already has a schema description. The narrative adds business-level semantics the schema cannot express, such as requiring department or employeeIds despite no JSON-schema 'required' fields, and explaining that the filter only changes returned rows while summary counts remain unfiltered.

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 opens with a specific computed resource: 'Vacation report for one department (or a list of employeeIds) and one calendar year', then enumerates the exact fields returned (balance, used YTD, planned, unplanned, longest block, 14-day flag). This level of specificity clearly differentiates it from siblings like bamboohr_time_off_balances or bamboohr_whos_out.

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?

It explicitly states when the tool can and cannot be used: 'A department or employeeIds is required — a company-wide overview in one call is not allowed, ask per department' and 'the group must fit the per-call record limit'. It also gives targeted feature usage for onlyMissingFourteenDayBlock. It does not explicitly name sibling tools as alternatives, so it stops short of a full 5.

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