Skip to main content
Glama
mikkmihkel

BambooHR MCP Server

by mikkmihkel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Table rows

bamboohr_table_rows
Read-onlyIdempotent

Retrieve employee table rows for a single employee, including job history, employment status, or custom tables. Requires employee ID and table alias; sensitive tables are excluded.

Instructions

Read the rows of an employee table for ONE employee: job history (jobInfo), employmentStatus, or any custom table (e.g. equipment, certificates). employeeId is required. Pay, compensation, bank, identity-document, health and similar tables are excluded by policy and are refused; money-type columns are dropped. Get valid table aliases from bamboohr_list_tables. Rows are unsorted; sort by date yourself.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tableYesTable alias, e.g. jobInfo, employmentStatus, customEquipment.
employeeIdYesInternal employee id. Required: this tool reads one employee at a time.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv4.1.0
    • changedInput schema / properties / employeeId / description
      Previous value: -"Internal employee id. Omit for all employees the key may see."New value: +"Internal employee id. Required: this tool reads one employee at a time."
    • changedInput schema / properties / table / description
      Previous value: -"Table alias, e.g. jobInfo, compensation, employmentStatus, customEquipment."New value: +"Table alias, e.g. jobInfo, employmentStatus, customEquipment."
    • removedInput schema / properties / table / minLength
      Removed value: -1
    • addedInput schema / properties / table / pattern
      Added value: +"^[A-Za-z0-9_]{1,64}$"
    • changedInput schema / required
      Previous value: -[
-  "table"
-]New value: +[
+  "table",
+  "employeeId"
+]
  2. First observedv3.0.0

TDQS

A4.9/5.0
Behavior5/5

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

Annotations already mark the tool read-only, idempotent, and non-destructive, and the description adds meaningful behavioral detail beyond that: policy-excluded tables are refused, money-type columns are dropped, one employee is handled per call, and row ordering is not guaranteed. No contradiction with annotations exists.

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 compact and front-loaded with the core action and scope, followed by exclusions, dependency guidance, and a sorting caveat. Every sentence carries necessary information with no filler.

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

Completeness5/5

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

For a read-only tool with only two well-documented parameters and no output schema, the description is complete: it states scope, required parameter, policy exclusions, how to get valid aliases, and the unsorted-row behavior. An agent has enough information to select and invoke the tool correctly.

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?

The input schema fully documents both parameters, so the baseline is 3. The description adds extra value by explaining that employeeId is required and scopes the call to a single employee, and it tells the agent to obtain table aliases from bamboohr_list_tables and expect money-type columns to be dropped—useful context beyond the schema.

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 verb and resource: 'Read the rows of an employee table for ONE employee,' and clarifies the table categories (jobInfo, employmentStatus, custom tables) as well as excluded tables. This clearly differentiates it from siblings like bamboohr_get_employee, bamboohr_list_employees, and bamboohr_list_tables.

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

Usage Guidelines5/5

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

The description gives explicit when-to-use context (one employee's table rows), explicit when-not-to-use exclusions (pay, compensation, bank, health tables are refused), and directs the agent to bamboohr_list_tables for valid aliases. It also warns that rows are unsorted, so the caller knows to sort by date.

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