Skip to main content
Glama

Bamboohr

by io.github.pipeworx-io

Remember

remember
Idempotent

Save data the agent will need to reuse later — across this conversation or across sessions. Use when you discover something worth carrying forward (a resolved ticker, a target address, a user preference, a research subject) so you don't have to look it up again. Stored as a key-value pair scoped by your identifier. Authenticated users get persistent memory; anonymous sessions retain memory for 24 hours. Pair with recall to retrieve later, forget to delete.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
keyYesMemory key (e.g., "subject_property", "target_ticker", "user_preference")
valueYesValue to store (any text — findings, addresses, preferences, notes)

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Beyond annotations (idempotent, not destructive), the description adds valuable behavioral details: persistence (authenticated users persistent, anonymous 24h), scoping ('scoped by your identifier'), and its role in a memory lifecycle. This enriches the agent's understanding without contradicting 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 three concise sentences that are front-loaded with the main purpose, followed by usage guidance and persistence semantics. No wasted words; every sentence provides distinct value.

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 simple tool with 2 required parameters and no output schema, the description is complete. It covers what, when, and how to use it, plus persistence and pairing with related tools. No critical gaps.

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

Parameters3/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 only adds that it's a key-value pair, which is already clear from the schema. It doesn't add new syntax or format details for parameters, so it doesn't exceed the baseline.

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 the tool's function: 'Save data the agent will need to reuse later.' It specifies the resource (key-value store) and distinguishes it from siblings like recall and forget by explicitly mentioning those as complementary tools.

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 gives explicit usage context ('Use when you discover something worth carrying forward') with concrete examples. It also points to alternatives (recall, forget). However, it doesn't explicitly state when not to use the tool, so it falls just short of a 5.

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

All Bamboohr toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

B3.4/5.0
Disambiguation3/5

The five BambooHR tools are distinct, but the set is dominated by overlapping Pipeworx/Polymarket search and research tools: ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded, and deep_research all serve similar lookup purposes, and polymarket_edges/polymarket_edge_tracker/polymarket_arbitrage/polymarket_fill_risk/polymarket_kalshi_spread occupy closely related prediction-market territory. Descriptions help differentiate them, but an agent could easily select the wrong one.

Naming Consistency2/5

Naming conventions are heavily mixed: camelCase (ai_visibility_check, ask_pipeworx_grounded), snake_case with varying verb positions (bamboohr_get_directory, list_subscriptions, resolve_entity), and domain-prefixed families that do not share a consistent pattern. Some tools are named by action (bet_research, compare_entities) rather than resource-object style, and the Pipeworx meta-tools follow a different convention than the BambooHR tools.

Tool Count2/5

36 tools is excessive for a server ostensibly named Bamboohr, and the vast majority are unrelated to HR—they cover general data research, prediction markets, AI visibility, and memory storage. The BambooHR-specific surface is only 5 tools buried inside a much larger third-party platform, making the count disproportionate to the stated server purpose.

Completeness2/5

The BambooHR domain is severely under-covered: read operations exist for directory, employees, employee files, and time off, but there are no create/update/delete operations, no time-off request management, no org chart access, no payroll or benefits tools, and no employee lifecycle workflows. Meanwhile, the many non-HR tools are extensive for their own domains but do not fill the obvious HR gaps.

Resources