Skip to main content
Glama
bitterpanda63

Officient MCP Server

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
OFFICIENT_TOKENYesYour Officient API token. Get it by inspecting a request and copying the bearer from the Authselfservice header.

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
list_peopleC

Get a paginated list of people from Officient

list_all_peopleB

Get all people from Officient with automatic pagination

get_person_detailC

Get detailed information about a specific person

get_employee_detailsA

Get details of the current logged-in employee (yourself)

list_coworkers_days_offB

Get coworkers' days off for a specific month

list_own_days_offA

Get your own days off for a specific year

get_all_salary_slipsC

Get all salary slip files

get_file_download_urlB

Get download URL for a file (e.g., salary slip PDF)

get_vacation_day_budgetsB

Get vacation day budgets for a specific year

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

B3.3/5.0

Scored across 9 tools

Disambiguation3/5

Most tools have distinct purposes, but list_all_people and list_people both list people with only pagination difference, which can confuse an agent. Similarly, get_employee_details and get_person_detail both return person details, though for self vs others. Descriptions help but overlap exists.

Naming Consistency4/5

Naming consistently uses 'get_' for single resources and 'list_' for collections. The only minor inconsistency is 'get_all_salary_slips' using 'get_all_' instead of 'list_', and 'list_all_people' using 'list_all_'. Overall pattern is clear.

Tool Count5/5

With 9 tools covering employee details, salary slips, vacation budgets, and days off, the set is well-scoped for a self-service HR server. No tools feel redundant or missing.

Completeness4/5

The tools cover core read operations for employee self-service: personal info, salary slips, vacation budgets, days off, and colleague lookup. Missing write operations (e.g., leave requests) are acceptable for a read-only server, but no tool for individual salary slip detail is a minor gap.

Maintenance

ActivityInactive
ResponsivenessNo issues