Skip to main content
Glama
Sign In

BambooHR MCP Server and API by Cotlet

by dev.cotlet
OverviewDiscussionsAdmin

Approve time off in BambooHR

bamboohr_approve_time_off
Read-onlyIdempotent

Approve time off in the user's own BambooHR account from ChatGPT, Claude or any AI agent. Returns how to do it in BambooHR step by step (screens, buttons, fields) and opens nothing by itself; then do it with the cotlet_browser_* tools in the user's BambooHR Cloud Browser. BambooHR's official API: Yes.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "bamboohr_approve_time_off"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior4/5

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

The description adds crucial context beyond the annotations: it returns instructions (screens, buttons, fields) and does not open or change anything by itself, so the agent must follow up with browser tools. This clarifies the read-only, advisory nature of the tool, which the annotations alone convey only implicitly.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is front-loaded with the core behavior and is reasonably concise. The final sentence 'BambooHR's official API: Yes' is somewhat unclear and could be trimmed, but overall the structure is effective.

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 simplicity (zero parameters, no output schema) and the annotations covering safety, the description provides enough detail about what the tool returns and how to proceed. It could be slightly more explicit about the output format, but it is largely complete for correct invocation.

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?

There are zero parameters, so the description does not need to explain parameter semantics. The schema is empty, and the description appropriately avoids discussing parameters.

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?

The description states it returns step-by-step instructions for approving time off in BambooHR and that it opens nothing by itself, distinguishing it from the cotlet_browser_* tools that perform the action. However, the opening phrase 'Approve time off' could momentarily suggest it performs the approval itself, slightly muddying the purpose.

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 clearly says to use this tool to get the steps and then use the cotlet_browser_* tools in the BambooHR Cloud Browser to actually do it. It doesn't explicitly address when not to use it (e.g., if the user already knows the steps), but the primary usage path is well defined.

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

All BambooHR MCP Server and API by Cotlet toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources