HR

Every HR tool, with the scope it needs, its arguments and the API operation it calls.

132 tools

Get HR analytics headcount

Read only

atlas_hr_analytics_headcount_get

HR analytics: current headcount snapshot (active employees grouped by department, location, and employment type).

Scope: hr:read
Calls: GET /v1/hr/reports/headcount
Example prompt: What is our headcount today by department?

Arguments

This tool takes no arguments.

Get HR analytics headcount timeseries

Read only

atlas_hr_analytics_headcount_timeseries_get

HR analytics: trailing-N-month headcount time-series (joins, exits, ending headcount per month).

Scope: hr:read
Calls: GET /v1/hr/reports/headcount/timeseries
Example prompt: Plot headcount month by month for the last 12 months.

Arguments

Field	Type	Required	Description
`months`	`integer`	No	Number of trailing months to include (1-60).

Get HR analytics leave utilization

Read only

atlas_hr_analytics_leave_utilization_get

HR analytics: leave utilization for a calendar year (entitled vs consumed days per leave type).

Scope: hr:read
Calls: GET /v1/hr/reports/leave-utilization
Example prompt: How is leave utilization tracking this year?

Arguments

Field	Type	Required	Description
`year`	`integer`	No	Calendar year (UTC). Defaults to the current year.

Get HR analytics turnover

Read only

atlas_hr_analytics_turnover_get

HR analytics: turnover rate for a date window (voluntary vs involuntary exits, average tenure).

Scope: hr:read
Calls: GET /v1/hr/reports/turnover
Example prompt: What was our turnover last quarter?

Arguments

Field	Type	Required	Description
`fromDate`	`string`	No	ISO date (inclusive) lower bound for the turnover window.
`toDate`	`string`	No	ISO date (inclusive) upper bound for the turnover window.

Clock HR attendance

Changes data

atlas_hr_attendance_clock

Record a clock-in or clock-out punch for an employee.

Scope: hr:write
Calls: POST /v1/hr/attendance/clock
Example prompt: Clock emp_abc in at 9am.

Arguments

Field	Type	Required	Description
`employeeId`	`string`	Yes	Employee id, from atlas_hr_employees_list.
`direction`	`"IN" \| "OUT"`	Yes	IN to clock in, OUT to clock out.
`source`	`"WEB" \| "MOBILE" \| "BIOMETRIC" \| "API"`	No	Where the punch came from. The API defaults to WEB.
`clockedAt`	`string (date-time)`	No	ISO-8601 timestamp of the punch. Omit to use the current time.
`latitude`	`number`	No
`longitude`	`number`	No
`notes`	`string`	No

Get HR attendance daily summary

Read only

atlas_hr_attendance_daily_summary_get

Get one-day worked-minutes summary for an employee.

Scope: hr:read
Calls: GET /v1/hr/attendance/daily/{employeeId}/{date}
Example prompt: How many hours did emp_abc work on Monday?

Arguments

Field	Type	Required	Description
`employeeId`	`string`	Yes
`date`	`string`	Yes	ISO date (YYYY-MM-DD).

List HR attendance logs

Read only

atlas_hr_attendance_logs_list

List attendance clock events. Filter by employee or date window.

Scope: hr:read
Calls: GET /v1/hr/attendance/logs
Example prompt: Show me emp_abc's attendance last week.

Arguments

Field	Type	Required	Description
`employeeId`	`string`	No
`startDate`	`string`	No	First day, YYYY-MM-DD.
`endDate`	`string`	No	Last day, YYYY-MM-DD.
`limit`	`integer`	No

List HR attendance shifts

Read only

atlas_hr_attendance_shifts_list

List shift templates configured in the tenant.

Scope: hr:read
Calls: GET /v1/hr/attendance/shifts
Example prompt: What shift patterns do we have?

Arguments

This tool takes no arguments.

List HR audit logs

Read only

atlas_hr_audit_logs_list

List the HR audit log. Filter by action, target, actor, or date window.

Scope: hr:read
Calls: GET /v1/hr/admin/audit
Example prompt: What HR actions happened today?

Arguments

Field	Type	Required	Description
`action`	`string`	No
`targetType`	`string`	No
`targetId`	`string`	No
`actorEmployeeId`	`string`	No
`fromDate`	`string`	No	ISO date lower bound.
`toDate`	`string`	No	ISO date upper bound.
`limit`	`integer`	No

Create HR candidates

Changes data

atlas_hr_candidates_create

Create a new candidate in the talent pool.

Scope: hr:write
Calls: POST /v1/hr/hiring/candidates
Example prompt: Add Raj Patel as a candidate, sourced from LinkedIn.

Arguments

Field	Type	Required	Description
`firstName`	`string`	Yes
`lastName`	`string`	Yes
`email`	`string (email)`	Yes
`phone`	`string`	No
`linkedinUrl`	`string (uri)`	No
`currentEmployer`	`string`	No
`currentLocation`	`string`	No
`noticePeriodDays`	`integer`	No
`expectedSalary`	`number`	No
`expectedCurrency`	`string`	No	Three-letter ISO 4217 currency code, for example INR.
`source`	`"CAREER_SITE" \| "REFERRAL" \| "AGENCY" \| "LINKEDIN" \| "INDEED" \| "OUTBOUND" \| "OTHER"`	No	Where the candidate came from. The API defaults to OTHER.
`consentGivenAt`	`string`	No	Date (YYYY-MM-DD) the candidate consented to data processing.
`tags`	`array of string`	No

Get HR candidates

Read only

atlas_hr_candidates_get

Fetch a single candidate by id.

Scope: hr:read
Calls: GET /v1/hr/hiring/candidates/{id}
Example prompt: Show me cand_xyz.

Arguments

Field	Type	Required	Description
`id`	`string`	Yes

List HR candidates

Read only

atlas_hr_candidates_list

List candidates in the talent pool. Free-text search supported.

Scope: hr:read
Calls: GET /v1/hr/hiring/candidates
Example prompt: Find candidates who mention Kubernetes.

Arguments

Field	Type	Required
`search`	`string`	No
`source`	`string`	No
`limit`	`integer`	No

List HR candidates scorecards

Read only

atlas_hr_candidates_scorecards_list

List interview scorecards filed for one candidate across all their interviews.

Scope: hr:read
Calls: GET /v1/hr/hiring/candidates/{id}/scorecards
Example prompt: What did interviewers say about cand_xyz?

Arguments

Field	Type	Required	Description
`candidateId`	`string`	Yes

Update HR candidates

Changes data

atlas_hr_candidates_update

Patch fields on a candidate record.

Scope: hr:write
Calls: PATCH /v1/hr/hiring/candidates/{id}
Example prompt: Update cand_xyz's phone number.

Arguments

Field	Type	Required	Description
`id`	`string`	Yes
`patch`	`object`	Yes	Fields to update. Omit a field to leave it unchanged.

Archive HR departments

Destructive

atlas_hr_departments_archive

Archive (soft-delete) a department by id.

Scope: hr:write
Calls: DELETE /v1/hr/departments/{id}
Example prompt: Archive the dept_legacy department.

Arguments

Field	Type	Required	Description
`id`	`string`	Yes

Create HR departments

Changes data

atlas_hr_departments_create

Create a new department, optionally nested under a parent.

Scope: hr:write
Calls: POST /v1/hr/departments
Example prompt: Create a Data Platform department under Engineering.

Arguments

Field	Type	Required	Description
`name`	`string`	Yes	Department name.
`code`	`string`	Yes	Short department code, for example ENG or FIN-OPS. Letters, digits, dot, underscore and hyphen only, 32 characters at most.
`description`	`string`	No	What the department does.
`parentId`	`string`	No	Parent department id, for a nested department.
`headEmployeeId`	`string`	No	Employee id of the department head.

List HR departments

Read only

atlas_hr_departments_list

List every department in the tenant.

Scope: hr:read
Calls: GET /v1/hr/departments
Example prompt: What departments do we have?

Arguments

This tool takes no arguments.

Update HR departments

Changes data

atlas_hr_departments_update

Patch fields on a department.

Scope: hr:write
Calls: PATCH /v1/hr/departments/{id}
Example prompt: Rename the Engineering department to Product Engineering.

Arguments

Field	Type	Required	Description
`id`	`string`	Yes	Department id.
`patch`	`object`	Yes	Fields to update. Any subset is accepted. The API does not accept null to clear a field.

Create HR emergency contacts

Changes data

atlas_hr_emergency_contacts_create

Add an emergency contact for an employee.

Scope: hr:write
Calls: POST /v1/hr/emergency-contacts
Example prompt: Add emp_abc's spouse as their emergency contact.

Arguments

Field	Type	Required	Description
`employeeId`	`string`	Yes
`name`	`string`	Yes
`relationship`	`string`	Yes	How the contact is related to the employee.
`phone`	`string`	Yes	Phone number to reach the contact.
`email`	`string (email)`	No

List HR emergency contacts

Read only

atlas_hr_emergency_contacts_list

List emergency contacts for one employee.

Scope: hr:read
Calls: GET /v1/hr/employees/{employeeId}/emergency-contacts
Example prompt: Who are emp_abc's emergency contacts?

Arguments

Field	Type	Required	Description
`employeeId`	`string`	Yes	Employee id.

Create HR employee documents

Changes data

atlas_hr_employee_documents_create

Attach a document to an employee, pointing at the object storage key of an already uploaded file.

Scope: hr:write
Calls: POST /v1/hr/documents
Example prompt: Attach the signed offer letter to emp_abc.

Arguments

Field	Type	Required	Description
`employeeId`	`string`	Yes	Employee id.
`title`	`string`	Yes	Document title.
`category`	`"CONTRACT" \| "ID_PROOF" \| "ADDRESS_PROOF" \| "EDUCATION" \| "EXPERIENCE" \| "POLICY_ACK" \| "OTHER"`	Yes	Document category.
`fileKey`	`string`	Yes	Object storage key of the file, which must already be uploaded. This is a key, not a URL.
`expiresAt`	`string (date-time)`	No	ISO 8601 date-time the document expires, for example 2027-03-31T00:00:00Z.

List HR employee documents

Read only

atlas_hr_employee_documents_list

List documents attached to one employee.

Scope: hr:read
Calls: GET /v1/hr/employees/{employeeId}/documents
Example prompt: What documents are on file for emp_abc?

Arguments

Field	Type	Required	Description
`employeeId`	`string`	Yes	Employee id.

Create HR employees

Changes data

atlas_hr_employees_create

Create a new employee record. Requires the employee number, name, work email, join date and employment type.

Scope: hr:write
Calls: POST /v1/hr/employees
Example prompt: Add Priya Sharma to engineering starting next Monday.

Arguments

Field	Type	Required	Description
`employeeNumber`	`string`	Yes	Tenant employee number, unique per tenant. Letters, digits, dot, underscore and hyphen only, 32 characters at most.
`firstName`	`string`	Yes	Given name.
`lastName`	`string`	Yes	Family name.
`workEmail`	`string (email)`	Yes	Work email address. Unique per tenant.
`joinedAt`	`string`	Yes	Date the employee joined (YYYY-MM-DD).
`employmentType`	`"FULL_TIME" \| "PART_TIME" \| "CONTRACT" \| "INTERN" \| "CONSULTANT"`	Yes	Employment type: FULL_TIME, PART_TIME, CONTRACT, INTERN or CONSULTANT.
`preferredName`	`string`	No	Name the employee prefers to be called.
`displayName`	`string`	No	Display name shown across Atlas.
`personalEmail`	`string (email)`	No	Personal email address.
`phone`	`string`	No	Phone number.
`confirmationAt`	`string`	No	Date employment was confirmed after probation (YYYY-MM-DD).
`departmentId`	`string`	No	Department id, from atlas_hr_departments_list.
`locationId`	`string`	No	Location id, from atlas_hr_locations_list.
`managerId`	`string`	No	Employee id of the manager, from atlas_hr_employees_list.
`status`	`"ACTIVE" \| "ON_LEAVE" \| "NOTICE" \| "TERMINATED"`	No	Initial status. The API defaults to ACTIVE when omitted.

List HR employees exit interviews

Read only

atlas_hr_employees_exit_interviews_list

HR-admin: list exit interview(s) for a specific employee. At most one will exist per employee.

Scope: hr:read
Calls: GET /v1/hr/exit-interviews/by-employee/{employeeId}
Example prompt: Pull emp_abc's exit interview.

Arguments

Field	Type	Required	Description
`employeeId`	`string`	Yes	Employee id whose exit interview(s) to list.

Get HR employees

Read only

atlas_hr_employees_get

Fetch a single employee by id.

Scope: hr:read
Calls: GET /v1/hr/employees/{employeeId}
Example prompt: Read me emp_abc's record.

Arguments

Field	Type	Required	Description
`employeeId`	`string`	Yes	Employee id.

Import HR employees

Changes data

atlas_hr_employees_import

Bulk-import employees from a CSV blob. Returns per-row created or error counts.

Scope: hr:write
Calls: POST /v1/hr/employees/bulk-import
Example prompt: Import this CSV of 40 new joiners.

Arguments

Field	Type	Required	Description
`csv`	`string`	Yes	CSV content with header row matching the bulk-import template.

List HR employees

Read only

atlas_hr_employees_list

List employees in the tenant. Filter by status, department, location, or free-text search.

Scope: hr:read
Calls: GET /v1/hr/employees
Example prompt: Show me every active engineer in the Mumbai office.

Arguments

Field	Type	Required	Description
`cursor`	`string`	No	Opaque pagination cursor from a previous page.
`limit`	`integer`	No	Max rows to return.
`status`	`string`	No	Filter by employmentStatus (e.g. ACTIVE, ON_LEAVE, TERMINATED).
`departmentId`	`string`	No	Filter by department id.
`locationId`	`string`	No	Filter by location id.
`search`	`string`	No	Free-text search on name or email.

Terminate HR employees

Destructive

atlas_hr_employees_terminate

Terminate an employee. Sets status to TERMINATED and records the termination date (today when omitted) and reason.

Scope: hr:write
Calls: DELETE /v1/hr/employees/{employeeId}
Example prompt: Terminate emp_abc effective 2026-07-31.

Arguments

Field	Type	Required	Description
`employeeId`	`string`	Yes	Employee id.
`terminatedAt`	`string`	No	Termination date. The API uses today when omitted (YYYY-MM-DD).
`terminationReason`	`string`	No	Reason for the termination.

Update HR employees

Changes data

atlas_hr_employees_update

Patch fields on an employee record.

Scope: hr:write
Calls: PATCH /v1/hr/employees/{employeeId}
Example prompt: Move emp_abc to the Platform team.

Arguments

Field	Type	Required	Description
`employeeId`	`string`	Yes	Employee id.
`patch`	`object`	Yes	Fields to update. Any subset is accepted. The API does not accept null to clear a field.

Create HR employment records

Changes data

atlas_hr_employment_records_create

Append a new employment history row for an employee (role change, promotion, transfer).

Scope: hr:write
Calls: POST /v1/hr/employment-records
Example prompt: Promote emp_abc to Senior Engineer effective next Monday.

Arguments

Field	Type	Required	Description
`employeeId`	`string`	Yes	Employee id.
`effectiveFrom`	`string`	Yes	Date this employment record takes effect (YYYY-MM-DD).
`effectiveTo`	`string`	No	Date this employment record ends. Omit for an open-ended record (YYYY-MM-DD).
`jobTitle`	`string`	Yes	Job title held under this record.
`employmentType`	`"FULL_TIME" \| "PART_TIME" \| "CONTRACT" \| "INTERN" \| "CONSULTANT"`	Yes	Employment type: FULL_TIME, PART_TIME, CONTRACT, INTERN or CONSULTANT.
`compensationCurrency`	`string`	Yes	ISO 4217 currency code of the compensation, for example INR or USD.
`compensationAnnualCTC`	`number`	No	Annual cost to company, in compensationCurrency.
`departmentId`	`string`	No	Department id.
`locationId`	`string`	No	Location id.
`managerId`	`string`	No	Employee id of the manager.
`notes`	`string`	No	Free-text notes about the record.

List HR employment records

Read only

atlas_hr_employment_records_list

List employment history rows for one employee.

Scope: hr:read
Calls: GET /v1/hr/employees/{employeeId}/employment-records
Example prompt: What is emp_abc's job history?

Arguments

Field	Type	Required	Description
`employeeId`	`string`	Yes	Employee id.

Run HR eSign sweep jobs

Changes data

atlas_hr_esign_sweep_jobs_run

Manually trigger the esign sweeper for this tenant (chases pending signatures).

Scope: hr:write
Calls: POST /v1/hr/admin/jobs/esign-sweep
Example prompt: Chase the pending esignatures.

Arguments

This tool takes no arguments.

List HR exit interviews

Read only

atlas_hr_exit_interviews_list

HR-admin: list submitted exit interviews. Filter by reason or conductedAt date range.

Scope: hr:read
Calls: GET /v1/hr/exit-interviews
Example prompt: Show me exit interviews from the last quarter.

Arguments

Field	Type	Required	Description
`reason`	`"VOLUNTARY" \| "INVOLUNTARY" \| "RELOCATION" \| "FAMILY" \| "COMPENSATION" \| "CAREER_GROWTH" \| "OTHER"`	No
`fromDate`	`string`	No	Inclusive lower bound on conductedAt (ISO date).
`toDate`	`string`	No	Inclusive upper bound on conductedAt (ISO date).
`limit`	`integer`	No

Submit HR exit interviews

Changes data

atlas_hr_exit_interviews_submit

HR-admin: submit an exit interview on behalf of a departing employee (reason, satisfaction, would-recommend, free-form responses).

Scope: hr:write
Calls: POST /v1/hr/exit-interviews
Example prompt: Log an exit interview for emp_abc: VOLUNTARY, satisfaction 4.

Arguments

Field	Type	Required	Description
`employeeId`	`string`	Yes	Employee id the interview is for.
`lastWorkingDay`	`string`	Yes
`reason`	`"VOLUNTARY" \| "INVOLUNTARY" \| "RELOCATION" \| "FAMILY" \| "COMPENSATION" \| "CAREER_GROWTH" \| "OTHER"`	Yes
`satisfaction`	`integer`	Yes	1-5 overall satisfaction.
`wouldRecommend`	`integer`	Yes	1-5 likelihood of recommending the company.
`responses`	`array of object`	No
`notes`	`string`	No

Create HR exports

Changes data

atlas_hr_exports_create

Kick off a new HR export job (returns the export id; poll for status).

Scope: hr:write
Calls: POST /v1/hr/admin/exports
Example prompt: Export all employees as CSV.

Arguments

Field	Type	Required	Description
`type`	`string`	No	Export kind (e.g. CSV, PDF).
`targetType`	`string`	No	What to export (e.g. EMPLOYEES, PAYSLIPS).

List HR exports

Read only

atlas_hr_exports_list

List previously generated HR exports.

Scope: hr:read
Calls: GET /v1/hr/admin/exports
Example prompt: Show me past HR exports.

Arguments

This tool takes no arguments.

List HR hiring pipelines

Read only

atlas_hr_hiring_pipelines_list

List hiring pipelines (stage definitions) configured in the tenant.

Scope: hr:read
Calls: GET /v1/hr/hiring/pipelines
Example prompt: What hiring pipelines do we use?

Arguments

This tool takes no arguments.

Create HR holidays

Changes data

atlas_hr_holidays_create

Create a tenant holiday for one country, identified by its ISO 3166-1 alpha-2 code.

Scope: hr:write
Calls: POST /v1/hr/holidays
Example prompt: Add Independence Day as a holiday on 15 Aug.

Arguments

Field	Type	Required	Description
`name`	`string`	Yes	Holiday name.
`date`	`string`	Yes	Holiday date (YYYY-MM-DD).
`countryCode`	`string`	Yes	ISO 3166-1 alpha-2 code of the country the holiday applies to, for example IN or US.
`description`	`string`	No	Optional note about the holiday.

Delete HR holidays

Destructive

atlas_hr_holidays_delete

Remove a tenant holiday by id.

Scope: hr:write
Calls: DELETE /v1/hr/holidays/{id}
Example prompt: Delete the cancelled holiday hol_xyz.

Arguments

Field	Type	Required	Description
`id`	`string`	Yes

List HR holidays

Read only

atlas_hr_holidays_list

List tenant holidays. Optionally filter by year or location.

Scope: hr:read
Calls: GET /v1/hr/holidays
Example prompt: What holidays are scheduled this year?

Arguments

Field	Type	Required	Description
`year`	`integer`	No
`countryCode`	`string`	No	Two-letter country code, for example IN or US.

Update HR holidays

Changes data

atlas_hr_holidays_update

Patch fields on a tenant holiday.

Scope: hr:write
Calls: PATCH /v1/hr/holidays/{id}
Example prompt: Mark next Friday as a tenant holiday.

Arguments

Field	Type	Required	Description
`id`	`string`	Yes	Holiday id.
`patch`	`object`	Yes	Fields to update. Any subset is accepted.

Create HR interview scorecards

Changes data

atlas_hr_interview_scorecards_create

File a structured interview scorecard with overall rating and recommendation.

Scope: hr:write
Calls: POST /v1/hr/hiring/interviews/{id}/scorecards
Example prompt: File a STRONG_YES scorecard on int_xyz.

Arguments

Field	Type	Required	Description
`interviewId`	`string`	Yes
`interviewerId`	`string`	Yes	Employee id of the interviewer filing the scorecard, normally the interviewer on the interview (see atlas_hr_interviews_list); list employees with atlas_hr_employees_list.
`overallRating`	`integer`	Yes	Overall rating from 1 to 5.
`recommendation`	`"STRONG_HIRE" \| "HIRE" \| "NO_HIRE" \| "STRONG_NO_HIRE"`	Yes
`strengths`	`string`	No
`concerns`	`string`	No
`notes`	`string`	No
`criteria`	`array of object`	No	Per-area ratings.

Delete HR interview scorecards

Destructive

atlas_hr_interview_scorecards_delete

Delete an interview scorecard by id.

Scope: hr:write
Calls: DELETE /v1/hr/hiring/scorecards/{id}
Example prompt: Delete the duplicate sc_xyz.

Arguments

Field	Type	Required	Description
`id`	`string`	Yes

Update HR interview scorecards

Changes data

atlas_hr_interview_scorecards_update

Patch fields on an interview scorecard.

Scope: hr:write
Calls: PATCH /v1/hr/hiring/scorecards/{id}
Example prompt: Update sc_xyz to add more notes.

Arguments

Field	Type	Required	Description
`id`	`string`	Yes
`patch`	`object`	Yes	Fields to update. Omit a field to leave it unchanged.

List HR interviews

Read only

atlas_hr_interviews_list

List interviews. Filter by application, candidate, or date window.

Scope: hr:read
Calls: GET /v1/hr/hiring/interviews
Example prompt: What interviews are on my calendar this week?

Arguments

Field	Type	Required	Description
`applicationId`	`string`	No
`interviewerId`	`string`	No	Only interviews this employee conducts.
`limit`	`integer`	No

Schedule HR interviews

Changes data

atlas_hr_interviews_schedule

Schedule an interview for one application with one interviewer.

Scope: hr:write
Calls: POST /v1/hr/hiring/interviews
Example prompt: Schedule a technical screen for app_xyz at 3pm Thursday.

Arguments

Field	Type	Required	Description
`applicationId`	`string`	Yes	Application id; list applications with atlas_hr_job_applications_list.
`interviewerId`	`string`	Yes	Employee id of the interviewer; list employees with atlas_hr_employees_list. One interviewer per interview.
`scheduledAt`	`string (date-time)`	Yes	ISO-8601 start date and time, with Z or a UTC offset.
`durationMins`	`integer`	No	Length in minutes. The API defaults to 45.
`mode`	`"PHONE" \| "VIDEO" \| "ONSITE"`	Yes	How the interview takes place.
`videoLink`	`string (uri)`	No
`location`	`string`	No

Update HR interviews

Changes data

atlas_hr_interviews_update

Patch fields on an interview (reschedule, change mode or location, record feedback).

Scope: hr:write
Calls: PATCH /v1/hr/hiring/interviews/{id}
Example prompt: Reschedule int_xyz to next Tuesday.

Arguments

Field	Type	Required	Description
`id`	`string`	Yes
`patch`	`object`	Yes	Fields to update. Omit a field to leave it unchanged.

Create HR job applications

Changes data

atlas_hr_job_applications_create

Attach a candidate to an opening as a new application.

Scope: hr:write
Calls: POST /v1/hr/hiring/applications
Example prompt: Apply cand_xyz to opn_xyz.

Arguments

Field	Type	Required	Description
`jobOpeningId`	`string`	Yes	Job opening id; list openings with atlas_hr_job_openings_list.
`candidateId`	`string`	Yes	Candidate id; list candidates with atlas_hr_candidates_list.
`referrerId`	`string`	No	Employee id of the person who referred the candidate; list employees with atlas_hr_employees_list.

Get HR job applications

Read only

atlas_hr_job_applications_get

Fetch a single application by id.

Scope: hr:read
Calls: GET /v1/hr/hiring/applications/{id}
Example prompt: Show me application app_xyz.

Arguments

Field	Type	Required	Description
`id`	`string`	Yes

List HR job applications

Read only

atlas_hr_job_applications_list

List applications. Filter by opening, candidate, status, or pipeline stage.

Scope: hr:read
Calls: GET /v1/hr/hiring/applications
Example prompt: Who is in the technical-screen stage for opn_xyz?

Arguments

Field	Type	Required	Description
`jobOpeningId`	`string`	No	Only applications for this job opening.
`candidateId`	`string`	No
`status`	`string`	No
`limit`	`integer`	No

Reject HR job applications

Changes data

atlas_hr_job_applications_reject

Reject an application with an optional reason.

Scope: hr:write
Calls: PATCH /v1/hr/hiring/applications/{id}/reject
Example prompt: Reject app_xyz: skills mismatch.

Arguments

Field	Type	Required	Description
`id`	`string`	Yes
`rejectionReason`	`string`	No

Transition HR job applications

Changes data

atlas_hr_job_applications_transition

Move an application to a different pipeline stage.

Scope: hr:write
Calls: PATCH /v1/hr/hiring/applications/{id}/advance
Example prompt: Advance app_xyz to the onsite stage.

Arguments

Field	Type	Required	Description
`id`	`string`	Yes
`currentStageId`	`string`	Yes	Id of the pipeline stage to move the application to. It must belong to the same pipeline as the current stage; list stages with atlas_hr_hiring_pipelines_list.

Accept HR job offers

Changes data

atlas_hr_job_offers_accept

Mark an offer accepted (typically called from the candidate portal).

Scope: hr:write
Calls: POST /v1/hr/hiring/offers/{id}/accept
Example prompt: Mark ofr_xyz as accepted.

Arguments

Field	Type	Required	Description
`id`	`string`	Yes

Create HR job offers

Changes data

atlas_hr_job_offers_create

Create a job offer attached to an application.

Scope: hr:write
Calls: POST /v1/hr/hiring/offers
Example prompt: Draft a 25 lakh INR offer for app_xyz with a Sept 1 start date.

Arguments

Field	Type	Required	Description
`applicationId`	`string`	Yes	Application id; list applications with atlas_hr_job_applications_list.
`compensationAnnualCTC`	`number`	Yes	Annual cost to company.
`compensationCurrency`	`string`	Yes	Three-letter ISO 4217 currency code, for example INR.
`expectedStartDate`	`string`	Yes	Expected joining date, YYYY-MM-DD.

Decline HR job offers

Changes data

atlas_hr_job_offers_decline

Mark an offer declined with an optional reason.

Scope: hr:write
Calls: POST /v1/hr/hiring/offers/{id}/decline
Example prompt: Decline ofr_xyz: candidate took another offer.

Arguments

Field	Type	Required	Description
`id`	`string`	Yes
`reason`	`string`	No

Get HR job offers

Read only

atlas_hr_job_offers_get

Fetch a single offer by id.

Scope: hr:read
Calls: GET /v1/hr/hiring/offers/{id}
Example prompt: Show me offer ofr_xyz.

Arguments

Field	Type	Required	Description
`id`	`string`	Yes

List HR job offers

Read only

atlas_hr_job_offers_list

List offers. Filter by application, candidate, or status.

Scope: hr:read
Calls: GET /v1/hr/hiring/offers
Example prompt: Which offers are still in DRAFT?

Arguments

Field	Type	Required
`applicationId`	`string`	No
`status`	`string`	No
`limit`	`integer`	No

Send HR job offers

Destructive

atlas_hr_job_offers_send

Send the offer to the candidate (emails the candidate, marks status SENT).

Scope: hr:write
Calls: POST /v1/hr/hiring/offers/{id}/send
Example prompt: Send offer ofr_xyz.

Arguments

Field	Type	Required	Description
`id`	`string`	Yes

Update HR job offers

Changes data

atlas_hr_job_offers_update

Patch fields on an offer (compensation, currency, expected start date).

Scope: hr:write
Calls: PATCH /v1/hr/hiring/offers/{id}
Example prompt: Bump ofr_xyz to 28 lakh.

Arguments

Field	Type	Required	Description
`id`	`string`	Yes
`patch`	`object`	Yes	Fields to update. Omit a field to leave it unchanged.

Create HR job openings

Changes data

atlas_hr_job_openings_create

Create a new job opening (DRAFT by default).

Scope: hr:write
Calls: POST /v1/hr/hiring/openings
Example prompt: Open a Senior Backend Engineer role in Bengaluru.

Arguments

Field	Type	Required	Description
`title`	`string`	Yes
`code`	`string`	Yes	Short requisition code unique to the opening, for example ENG-042.
`jobType`	`"FULL_TIME" \| "PART_TIME" \| "CONTRACT" \| "INTERN"`	Yes	Employment type of the role.
`description`	`string`	Yes	Role description shown to candidates.
`status`	`"DRAFT" \| "OPEN" \| "ON_HOLD" \| "FILLED" \| "CLOSED"`	No	Opening status. The API defaults a new opening to DRAFT.
`headcount`	`integer`	No	Number of positions. Defaults to 1.
`requirements`	`string`	No
`responsibilities`	`string`	No
`departmentId`	`string`	No	Department id; list departments with atlas_hr_departments_list.
`locationId`	`string`	No	Work location id; list locations with atlas_hr_locations_list.
`hiringManagerEmployeeId`	`string`	No	Employee id of the hiring manager; list employees with atlas_hr_employees_list.
`recruiterEmployeeId`	`string`	No	Employee id of the recruiter; list employees with atlas_hr_employees_list.
`compensationRangeMin`	`number`	No
`compensationRangeMax`	`number`	No
`compensationCurrency`	`string`	No	Three-letter ISO 4217 currency code, for example INR.

Get HR job openings

Read only

atlas_hr_job_openings_get

Fetch a single job opening by id.

Scope: hr:read
Calls: GET /v1/hr/hiring/openings/{id}
Example prompt: Show me opn_xyz.

Arguments

Field	Type	Required	Description
`id`	`string`	Yes

List HR job openings

Read only

atlas_hr_job_openings_list

List job openings. Filter by status, department, or location.

Scope: hr:read
Calls: GET /v1/hr/hiring/openings
Example prompt: What roles are open right now?

Arguments

Field	Type	Required	Description
`status`	`string`	No
`search`	`string`	No	Text to search the openings for.
`limit`	`integer`	No

Update HR job openings

Changes data

atlas_hr_job_openings_update

Patch fields on a job opening.

Scope: hr:write
Calls: PATCH /v1/hr/hiring/openings/{id}
Example prompt: Move opn_xyz to OPEN.

Arguments

Field	Type	Required	Description
`id`	`string`	Yes
`patch`	`object`	Yes	Fields to update. Omit a field to leave it unchanged.

Run HR leave accrual jobs

Changes data

atlas_hr_leave_accrual_jobs_run

Manually trigger the leave-accrual background job for this tenant.

Scope: hr:write
Calls: POST /v1/hr/admin/jobs/leave-accrual
Example prompt: Run the leave accrual now.

Arguments

This tool takes no arguments.

List HR leave balances

Read only

atlas_hr_leave_balances_list

List leave balances. Filter by employee or year.

Scope: hr:read
Calls: GET /v1/hr/leave/balances
Example prompt: How much annual leave does emp_abc have left?

Arguments

Field	Type	Required	Description
`employeeId`	`string`	No
`year`	`integer`	No

Create HR leave policies

Changes data

atlas_hr_leave_policies_create

Create a leave policy: kind of leave, accrual, annual limit, carry-forward limit and approval rules.

Scope: hr:write
Calls: POST /v1/hr/leave/policies
Example prompt: Create an annual leave policy of 22 days a year.

Arguments

Field	Type	Required	Description
`name`	`string`	Yes
`description`	`string`	No
`leaveType`	`"CASUAL" \| "SICK" \| "EARNED" \| "MATERNITY" \| "PATERNITY" \| "BEREAVEMENT" \| "COMPENSATORY" \| "UNPAID" \| "CUSTOM"`	Yes	Kind of leave this policy governs.
`accrualType`	`"NONE" \| "MONTHLY" \| "QUARTERLY" \| "ANNUAL"`	No	How often leave accrues. The API defaults to NONE.
`accrualRate`	`number`	No	Days accrued each accrual period. The API defaults to 0.
`annualLimitDays`	`number`	No	Maximum days that can be taken in a year. The API defaults to 0.
`carryForwardMaxDays`	`number`	No	Maximum unused days carried into the next year. The API defaults to 0.
`requiresApproval`	`boolean`	No	Whether requests need approval. The API defaults to true.
`autoApproveBelowDays`	`integer`	No	Requests of this many days or fewer are approved automatically.
`appliesToEmploymentTypes`	`array of "FULL_TIME" \| "PART_TIME" \| "CONTRACT" \| "INTERN" \| "CONSULTANT"`	No	Employment types the policy applies to. Empty or omitted means all.

List HR leave policies

Read only

atlas_hr_leave_policies_list

List leave policies configured in the tenant.

Scope: hr:read
Calls: GET /v1/hr/leave/policies
Example prompt: What leave policies do we offer?

Arguments

This tool takes no arguments.

Update HR leave policies

Changes data

atlas_hr_leave_policies_update

Patch fields on a leave policy.

Scope: hr:write
Calls: PATCH /v1/hr/leave/policies/{id}
Example prompt: Bump annual leave from 20 to 22 days.

Arguments

Field	Type	Required	Description
`id`	`string`	Yes	Leave policy id, from atlas_hr_leave_policies_list.
`patch`	`object`	Yes	Fields to update. Omitted fields are left unchanged.

Approve HR leave requests

Changes data

atlas_hr_leave_requests_approve

Approve a PENDING leave request. Decrements the employee balance.

Scope: hr:write
Calls: PATCH /v1/hr/leave/requests/{id}/approve
Example prompt: Approve leave request lvr_xyz.

Arguments

Field	Type	Required	Description
`id`	`string`	Yes	Leave request id.

Create HR leave requests

Changes data

atlas_hr_leave_requests_create

Create a leave request for an employee against a leave policy. Status starts as PENDING.

Scope: hr:write
Calls: POST /v1/hr/leave/requests
Example prompt: File annual leave for emp_abc from Dec 20 to Dec 31.

Arguments

Field	Type	Required	Description
`employeeId`	`string`	Yes	Employee id, from atlas_hr_employees_list.
`leavePolicyId`	`string`	Yes	Leave policy the request is charged against, from atlas_hr_leave_policies_list. The policy decides the kind of leave.
`startDate`	`string`	Yes	First day of leave (YYYY-MM-DD).
`endDate`	`string`	Yes	Last day of leave (YYYY-MM-DD), on or after startDate.
`durationDays`	`number`	No	Days of leave. Omit to let the API count the days from the date range.
`reason`	`string`	No

List HR leave requests

Read only

atlas_hr_leave_requests_list

List leave requests. Filter by employee or status.

Scope: hr:read
Calls: GET /v1/hr/leave/requests
Example prompt: What leave requests are pending approval?

Arguments

Field	Type	Required
`employeeId`	`string`	No
`status`	`"PENDING" \| "APPROVED" \| "REJECTED" \| "CANCELLED"`	No
`limit`	`integer`	No

Reject HR leave requests

Changes data

atlas_hr_leave_requests_reject

Reject a PENDING leave request with an optional reason.

Scope: hr:write
Calls: PATCH /v1/hr/leave/requests/{id}/reject
Example prompt: Reject lvr_xyz: dates overlap a release.

Arguments

Field	Type	Required	Description
`id`	`string`	Yes	Leave request id.
`rejectionReason`	`string`	No	Reason recorded on the request and shown to the employee.

Generate HR letters

Changes data

atlas_hr_letters_generate

Generate an HR letter (OFFER, JOINING, INCREMENT, EXPERIENCE, or RELIEVING) for one employee. Returns the persisted letter record; use atlas_hr_letters_pdf_url_get to fetch the bytes.

Scope: hr:write
Calls: POST /v1/hr/letters
Example prompt: Generate an offer letter for emp_abc with a 42 LPA INR annual CTC.

Arguments

Field	Type	Required
`employeeId`	`string`	Yes
`type`	`"OFFER" \| "JOINING" \| "INCREMENT" \| "EXPERIENCE" \| "RELIEVING"`	Yes
`variables`	`object`	No

List HR letters

Read only

atlas_hr_letters_list

List every HR letter that has been generated for one employee, newest first.

Scope: hr:read
Calls: GET /v1/hr/letters
Example prompt: Show me every letter generated for emp_abc.

Arguments

Field	Type	Required	Description
`employeeId`	`string`	Yes	Employee id whose letters to list.

Get HR letters PDF URL

Read only

atlas_hr_letters_pdf_url_get

Return the API path for the PDF bytes of one HR letter. Compose with the tenant API base URL and an Authorization header to download.

Scope: hr:read
Calls: GET /v1/hr/letters/{id}/pdf
Example prompt: Give me the PDF URL for HR letter let_xyz.

Arguments

Field	Type	Required	Description
`id`	`string`	Yes	HR letter id.

Revoke HR letters

Destructive

atlas_hr_letters_revoke

Revoke a previously issued HR letter. The row stays for audit; the revoked flag flips to true.

Scope: hr:write
Calls: PATCH /v1/hr/letters/{id}/revoke
Example prompt: Revoke HR letter let_xyz because it was issued with the wrong designation.

Arguments

Field	Type	Required	Description
`id`	`string`	Yes	HR letter id.

Archive HR locations

Destructive

atlas_hr_locations_archive

Archive (soft-delete) a workplace location by id.

Scope: hr:write
Calls: DELETE /v1/hr/locations/{id}
Example prompt: Archive the loc_old location.

Arguments

Field	Type	Required	Description
`id`	`string`	Yes

Create HR locations

Changes data

atlas_hr_locations_create

Create a new workplace location.

Scope: hr:write
Calls: POST /v1/hr/locations
Example prompt: Add a Bengaluru office at the Indiranagar address.

Arguments

Field	Type	Required	Description
`name`	`string`	Yes	Location name, for example Bengaluru office.
`addressLine1`	`string`	Yes	First line of the street address.
`addressLine2`	`string`	No	Second line of the street address.
`city`	`string`	Yes	City.
`state`	`string`	Yes	State, province or region.
`country`	`string`	Yes	Country, 2 to 80 characters (an ISO code or the name).
`postalCode`	`string`	Yes	Postal or ZIP code.
`timezone`	`string`	Yes	IANA time zone, for example Asia/Kolkata.
`isHQ`	`boolean`	No	Whether this is the headquarters. The API defaults to false.

List HR locations

Read only

atlas_hr_locations_list

List every workplace location in the tenant.

Scope: hr:read
Calls: GET /v1/hr/locations
Example prompt: List our offices.

Arguments

This tool takes no arguments.

Update HR locations

Changes data

atlas_hr_locations_update

Patch fields on a workplace location.

Scope: hr:write
Calls: PATCH /v1/hr/locations/{id}
Example prompt: Update the Mumbai office address.

Arguments

Field	Type	Required	Description
`id`	`string`	Yes
`patch`	`object`	Yes	Fields to update.

Create HR onboarding checklists

Changes data

atlas_hr_onboarding_checklists_create

Create a new onboarding checklist template with an ordered task list.

Scope: hr:write
Calls: POST /v1/hr/onboarding/checklists
Example prompt: Create an engineering onboarding checklist with these 8 tasks.

Arguments

Field	Type	Required	Description
`name`	`string`	Yes
`description`	`string`	No
`appliesToEmploymentTypes`	`array of "FULL_TIME" \| "PART_TIME" \| "CONTRACT" \| "INTERN" \| "CONSULTANT"`	No	Employment types the checklist applies to. Empty or omitted means every type.
`tasks`	`array of object`	Yes	Ordered list of onboarding tasks.

List HR onboarding checklists

Read only

atlas_hr_onboarding_checklists_list

List onboarding checklist templates available in the tenant.

Scope: hr:read
Calls: GET /v1/hr/onboarding/checklists
Example prompt: What onboarding templates do we have?

Arguments

This tool takes no arguments.

Complete HR onboarding tasks

Changes data

atlas_hr_onboarding_tasks_complete

Mark one onboarding task as complete.

Scope: hr:write
Calls: POST /v1/hr/onboarding/{onboardingId}/tasks/{taskId}/complete
Example prompt: Mark the IT-account task for emp_abc as done.

Arguments

Field	Type	Required	Description
`onboardingId`	`string`	Yes
`taskId`	`string`	Yes

Reopen HR onboarding tasks

Changes data

atlas_hr_onboarding_tasks_reopen

Re-open one onboarding task that was previously completed.

Scope: hr:write
Calls: POST /v1/hr/onboarding/{onboardingId}/tasks/{taskId}/uncomplete
Example prompt: Re-open the IT-account task for emp_abc.

Arguments

Field	Type	Required	Description
`onboardingId`	`string`	Yes
`taskId`	`string`	Yes

List HR onboardings

Read only

atlas_hr_onboardings_list

List in-progress and completed onboarding journeys. Optionally filter by employee.

Scope: hr:read
Calls: GET /v1/hr/onboarding
Example prompt: Who is currently onboarding?

Arguments

Field	Type	Required	Description
`employeeId`	`string`	No

Start HR onboardings

Changes data

atlas_hr_onboardings_start

Start an onboarding journey for an employee against a checklist template.

Scope: hr:write
Calls: POST /v1/hr/onboarding
Example prompt: Start emp_abc on the engineering onboarding checklist.

Arguments

Field	Type	Required	Description
`employeeId`	`string`	Yes	Employee id.
`checklistId`	`string`	Yes	Onboarding checklist id, from atlas_hr_onboarding_checklists_list.

Get HR org chart

Read only

atlas_hr_org_chart_get

Get the tenant org chart derived from Employee manager relationships.

Scope: hr:read
Calls: GET /v1/hr/org-chart
Example prompt: Show me the HR org chart.

Arguments

This tool takes no arguments.

Create HR performance cycles

Changes data

atlas_hr_performance_cycles_create

Create a new performance cycle with a name, a review period and an optional template.

Scope: hr:write
Calls: POST /v1/hr/performance/cycles
Example prompt: Create a Q4 review cycle with self, manager, and peer reviews.

Arguments

Field	Type	Required	Description
`name`	`string`	Yes
`startDate`	`string`	Yes	First day of the review period (YYYY-MM-DD).
`endDate`	`string`	Yes	Last day of the review period (YYYY-MM-DD).
`template`	`object`	No	Review template for the cycle, as a JSON object. The API defaults to {}.

Get HR performance cycles

Read only

atlas_hr_performance_cycles_get

Fetch a single performance cycle by id.

Scope: hr:read
Calls: GET /v1/hr/performance/cycles/{id}
Example prompt: Show me cycle cyc_xyz.

Arguments

Field	Type	Required	Description
`id`	`string`	Yes

List HR performance cycles

Read only

atlas_hr_performance_cycles_list

List performance cycles.

Scope: hr:read
Calls: GET /v1/hr/performance/cycles
Example prompt: What performance cycles are active?

Arguments

Field	Type	Required	Description
`status`	`string`	No
`limit`	`integer`	No

Start HR performance cycles

Changes data

atlas_hr_performance_cycles_start

Kick off a performance cycle for chosen employees, or for every active employee. Creates Reviews + Responses.

Scope: hr:write
Calls: POST /v1/hr/perf/cycles/{id}/kickoff
Example prompt: Kick off the Q4 cycle for the engineering team.

Arguments

Field	Type	Required	Description
`id`	`string`	Yes	Cycle id, from atlas_hr_performance_cycles_list.
`employeeIds`	`array of string`	No	Employees to include, from atlas_hr_employees_list. Omit to include every active employee.
`includeManager`	`boolean`	No	Whether to queue a manager response alongside each self review. The API defaults to true.

Create HR performance goals

Changes data

atlas_hr_performance_goals_create

Create a performance goal for an employee.

Scope: hr:write
Calls: POST /v1/hr/performance/goals
Example prompt: Set an OKR for emp_abc to ship the migration by Q4.

Arguments

Field	Type	Required	Description
`employeeId`	`string`	Yes	Employee id, from atlas_hr_employees_list.
`cycleId`	`string`	No	Performance cycle id, from atlas_hr_performance_cycles_list.
`parentGoalId`	`string \| null`	No	Parent goal id, from atlas_hr_performance_goals_list. Null detaches the goal from its parent.
`title`	`string`	Yes
`description`	`string`	No
`targetMetric`	`string`	No	How success is measured, in words (for example "12 renewals signed").
`weight`	`number`	No	Relative weight of the goal. The API defaults to 1.
`status`	`"NEW" \| "IN_PROGRESS" \| "AT_RISK" \| "COMPLETED" \| "ABANDONED"`	No	Progress status. The API defaults to NEW.
`dueDate`	`string`	No	Due date (YYYY-MM-DD).

List HR performance goals

Read only

atlas_hr_performance_goals_list

List performance goals. Filter by employee, status, or cycle.

Scope: hr:read
Calls: GET /v1/hr/performance/goals
Example prompt: What goals does emp_abc have this quarter?

Arguments

Field	Type	Required
`employeeId`	`string`	No
`status`	`string`	No
`cycleId`	`string`	No
`limit`	`integer`	No

Update HR performance goals

Changes data

atlas_hr_performance_goals_update

Patch fields on a performance goal (title, status, target metric, weight, due date).

Scope: hr:write
Calls: PATCH /v1/hr/performance/goals/{id}
Example prompt: Mark goal gol_xyz as on-track at 60% progress.

Arguments

Field	Type	Required	Description
`id`	`string`	Yes	Goal id, from atlas_hr_performance_goals_list.
`patch`	`object`	Yes	Fields to update. Omitted fields are left unchanged.

Submit HR performance review responses

Changes data

atlas_hr_performance_review_responses_submit

Submit answers for a performance review response.

Scope: hr:write
Calls: PATCH /v1/hr/perf/responses/{id}
Example prompt: Submit my self-review for emp_abc.

Arguments

Field	Type	Required	Description
`id`	`string`	Yes	Response id, from atlas_me_performance_review_responses_list.
`responses`	`array of object`	Yes	Per-question answers, each with a rating, comments, or both.

Finalize HR performance reviews

Changes data

atlas_hr_performance_reviews_finalize

Finalize a performance review with its final rating (all responses collected, manager signs off).

Scope: hr:write
Calls: PATCH /v1/hr/perf/reviews/{id}/finalize
Example prompt: Finalize emp_abc's Q4 review at a 4 out of 5.

Arguments

Field	Type	Required	Description
`id`	`string`	Yes	Review id, from atlas_hr_performance_reviews_list.
`finalRating`	`number`	Yes	Final rating for the review, from 0 to 10.

List HR performance reviews

Read only

atlas_hr_performance_reviews_list

List performance reviews. Filter by cycle, employee, or status.

Scope: hr:read
Calls: GET /v1/hr/performance/reviews
Example prompt: Which Q4 reviews are still in progress?

Arguments

Field	Type	Required
`cycleId`	`string`	No
`employeeId`	`string`	No
`status`	`string`	No
`limit`	`integer`	No

List HR policies acknowledgements

Read only

atlas_hr_policies_acknowledgements_list

HR-admin: list every employee acknowledgement recorded against a policy (for audit).

Scope: hr:read
Calls: GET /v1/hr/policies/{id}/acknowledgements
Example prompt: Who has acknowledged the code-of-conduct policy?

Arguments

Field	Type	Required	Description
`id`	`string`	Yes

Archive HR policies

Changes data

atlas_hr_policies_archive

HR-admin: retire a policy, optionally pointing at its replacement. Stops new acknowledgements.

Scope: hr:write
Calls: PATCH /v1/hr/policies/{id}/supersede
Example prompt: Supersede the old travel-policy with the 2026 version.

Arguments

Field	Type	Required	Description
`id`	`string`	Yes
`supersededByPolicyId`	`string`	No	Optional replacement policy id. Omit to retire without a successor.

Create HR policies

Changes data

atlas_hr_policies_create

HR-admin: create a new policy in the library (version 1, optional e-acknowledgement).

Scope: hr:write
Calls: POST /v1/hr/policies
Example prompt: Publish a new remote-work policy effective next Monday.

Arguments

Field	Type	Required	Description
`slug`	`string`	Yes	Stable kebab-case identifier (a-z, 0-9, -).
`title`	`string`	Yes
`category`	`string`	Yes	Free-text grouping, e.g. "Conduct", "Leave".
`body`	`string`	Yes	Markdown body of the policy.
`requiresAcknowledgement`	`boolean`	No	If true, employees must e-acknowledge to clear their queue.
`effectiveFrom`	`string`	Yes	Date the policy takes effect.

Get HR policies

Read only

atlas_hr_policies_get

HR-admin: fetch a single policy by its stable slug (returns current version).

Scope: hr:read
Calls: GET /v1/hr/policies/{slug}
Example prompt: Show me the leave-policy policy.

Arguments

Field	Type	Required	Description
`slug`	`string`	Yes

List HR policies

Read only

atlas_hr_policies_list

HR-admin: list policies in the company library. Filter by category or include superseded.

Scope: hr:read
Calls: GET /v1/hr/policies
Example prompt: What HR policies do we currently publish?

Arguments

Field	Type	Required	Description
`category`	`string`	No
`includeSuperseded`	`boolean`	No	Admin-only: include retired policies in the result.

Update HR policies

Changes data

atlas_hr_policies_update

HR-admin: patch a policy. Bumps version and invalidates every prior acknowledgement.

Scope: hr:write
Calls: PATCH /v1/hr/policies/{id}
Example prompt: Update the code-of-conduct policy body.

Arguments

Field	Type	Required	Description
`id`	`string`	Yes
`patch`	`object`	Yes	At least one field. Bumps version and invalidates prior acknowledgements.

Approve HR probations

Changes data

atlas_hr_probations_approve

HR-admin: confirm a probation as successfully passed. Moves the record from PENDING or EXTENDED to CONFIRMED.

Scope: hr:write
Calls: PATCH /v1/hr/probations/{id}/confirm
Example prompt: Confirm probation prb_xyz.

Arguments

Field	Type	Required	Description
`id`	`string`	Yes

Extend HR probations

Changes data

atlas_hr_probations_extend

HR-admin: extend the probation window to a new end date for further evaluation. Status moves to EXTENDED.

Scope: hr:write
Calls: PATCH /v1/hr/probations/{id}/extend
Example prompt: Extend probation prb_xyz by 30 days.

Arguments

Field	Type	Required	Description
`id`	`string`	Yes
`extendedToDate`	`string`	Yes	New probation end date (YYYY-MM-DD).
`notes`	`string`	No

Get HR probations

Read only

atlas_hr_probations_get

HR-admin: fetch a single probation record by id, including status, extension history, and termination reason.

Scope: hr:read
Calls: GET /v1/hr/probations/{id}
Example prompt: Show me probation prb_xyz.

Arguments

Field	Type	Required	Description
`id`	`string`	Yes

List HR probations

Read only

atlas_hr_probations_list

HR-admin: list probation records for the tenant. Filter by status (PENDING, CONFIRMED, EXTENDED, TERMINATED) or employee id.

Scope: hr:read
Calls: GET /v1/hr/probations
Example prompt: Who is currently on probation?

Arguments

Field	Type	Required	Description
`status`	`"PENDING" \| "CONFIRMED" \| "EXTENDED" \| "TERMINATED"`	No
`employeeId`	`string`	No

Start HR probations

Changes data

atlas_hr_probations_start

HR-admin: initiate a probation window for a newly joined or transferred employee. Lands in PENDING.

Scope: hr:write
Calls: POST /v1/hr/probations
Example prompt: Start a 3-month probation for emp_abc from 1 Jul.

Arguments

Field	Type	Required	Description
`employeeId`	`string`	Yes
`startDate`	`string`	Yes	Probation start date (YYYY-MM-DD).
`endDate`	`string`	Yes	Probation end date (YYYY-MM-DD).
`notes`	`string`	No

Terminate HR probations

Destructive

atlas_hr_probations_terminate

HR-admin: terminate a probation unsuccessfully with a required reason. Status moves to TERMINATED.

Scope: hr:write
Calls: PATCH /v1/hr/probations/{id}/terminate
Example prompt: Terminate probation prb_xyz: performance below bar.

Arguments

Field	Type	Required	Description
`id`	`string`	Yes
`reason`	`string`	Yes	Reason for termination of probation.

Approve HR reimbursement claims

Changes data

atlas_hr_reimbursement_claims_approve

Approve a SUBMITTED reimbursement claim. Stamps the approver and timestamp.

Scope: hr:write
Calls: PATCH /v1/hr/reimbursements/claims/{id}/approve
Example prompt: Approve reimbursement claim rc_xyz.

Arguments

Field	Type	Required	Description
`id`	`string`	Yes	Reimbursement claim id.

Create HR reimbursement claims

Changes data

atlas_hr_reimbursement_claims_create

Create a reimbursement claim on behalf of an employee. Pass submit=true to file it directly.

Scope: hr:write
Calls: POST /v1/hr/reimbursements/claims
Example prompt: Log a 1200 INR fuel claim for emp_abc on May 14.

Arguments

Field	Type	Required	Description
`employeeId`	`string`	Yes
`category`	`"MILEAGE" \| "MEALS" \| "FUEL" \| "TRAVEL" \| "EQUIPMENT" \| "MEDICAL" \| "COMMS" \| "OTHER"`	Yes
`amount`	`number`	Yes
`currency`	`string`	No
`claimedOn`	`string`	Yes	ISO date (YYYY-MM-DD) the expense was incurred.
`description`	`string`	No
`submit`	`boolean`	No	If true, file the claim directly in SUBMITTED state.

List HR reimbursement claims

Read only

atlas_hr_reimbursement_claims_list

List reimbursement claims across the tenant. Filter by status, employee, year, or limit.

Scope: hr:read
Calls: GET /v1/hr/reimbursements/claims
Example prompt: Which reimbursement claims are pending approval?

Arguments

Field	Type	Required
`status`	`"DRAFT" \| "SUBMITTED" \| "APPROVED" \| "REJECTED" \| "PAID"`	No
`employeeId`	`string`	No
`year`	`integer`	No
`limit`	`integer`	No

Record HR reimbursement claims payment

Changes data

atlas_hr_reimbursement_claims_payment_record

Mark an APPROVED reimbursement claim as PAID and optionally link the payslip it was paid in.

Scope: hr:write
Calls: PATCH /v1/hr/reimbursements/claims/{id}/mark-paid
Example prompt: Mark rc_xyz paid in payslip ps_jun26.

Arguments

Field	Type	Required	Description
`id`	`string`	Yes
`payslipId`	`string`	No	Optional payslip the claim was paid in.

Reject HR reimbursement claims

Changes data

atlas_hr_reimbursement_claims_reject

Reject a SUBMITTED reimbursement claim with a required reason.

Scope: hr:write
Calls: PATCH /v1/hr/reimbursements/claims/{id}/reject
Example prompt: Reject rc_xyz: out of policy.

Arguments

Field	Type	Required	Description
`id`	`string`	Yes
`reason`	`string`	Yes	Why the claim is being rejected.

Submit HR reimbursement claims

Changes data

atlas_hr_reimbursement_claims_submit

Push a DRAFT reimbursement claim to SUBMITTED so HR can approve it.

Scope: hr:write
Calls: PATCH /v1/hr/reimbursements/claims/{id}/submit
Example prompt: Submit reimbursement claim rc_xyz.

Arguments

Field	Type	Required	Description
`id`	`string`	Yes	Reimbursement claim id.

Get HR reports headcount

Read only

atlas_hr_reports_headcount_get

Current headcount snapshot broken down by department, location, employment type.

Scope: hr:read
Calls: GET /v1/hr/reports/headcount
Example prompt: What is our headcount today?

Arguments

This tool takes no arguments.

Get HR reports headcount timeseries

Read only

atlas_hr_reports_headcount_timeseries_get

Headcount month-by-month for the last N months (default 12, max 60).

Scope: hr:read
Calls: GET /v1/hr/reports/headcount/timeseries
Example prompt: Plot our headcount over the last 24 months.

Arguments

Field	Type	Required	Description
`months`	`integer`	No

Get HR reports leave utilization

Read only

atlas_hr_reports_leave_utilization_get

Leave utilization analytics for the chosen calendar year.

Scope: hr:read
Calls: GET /v1/hr/reports/leave-utilization
Example prompt: How is leave utilization tracking this year?

Arguments

Field	Type	Required	Description
`year`	`integer`	No

Get HR reports turnover

Read only

atlas_hr_reports_turnover_get

Turnover analytics: joiners, leavers and net change in a date window.

Scope: hr:read
Calls: GET /v1/hr/reports/turnover
Example prompt: What was our turnover last quarter?

Arguments

Field	Type	Required	Description
`fromDate`	`string`	No
`toDate`	`string`	No

Approve HR role changes HR

Changes data

atlas_hr_role_changes_hr_approve

HR-approve a MANAGER_APPROVED role-change. Atomically writes the new title / department / location / manager onto the Employee row and stamps the request APPLIED.

Scope: hr:write
Calls: PATCH /v1/hr/role-changes/{id}/hr-approve
Example prompt: HR-approve role change rc_xyz.

Arguments

Field	Type	Required	Description
`id`	`string`	Yes

List HR role changes

Read only

atlas_hr_role_changes_list

List employee role-change requests. Filter by employee or status (PENDING / MANAGER_APPROVED / HR_APPROVED / REJECTED / APPLIED).

Scope: hr:read
Calls: GET /v1/hr/role-changes
Example prompt: Which role-change requests are still pending HR approval?

Arguments

Field	Type	Required	Description
`employeeId`	`string`	No
`status`	`"PENDING" \| "MANAGER_APPROVED" \| "HR_APPROVED" \| "REJECTED" \| "APPLIED"`	No

Approve HR role changes manager

Changes data

atlas_hr_role_changes_manager_approve

Manager-approve a PENDING role-change request. The requester cannot self-approve.

Scope: hr:write
Calls: PATCH /v1/hr/role-changes/{id}/manager-approve
Example prompt: Manager-approve role change rc_xyz.

Arguments

Field	Type	Required	Description
`id`	`string`	Yes

Reject HR role changes

Changes data

atlas_hr_role_changes_reject

HR: reject a role-change request with a required reason.

Scope: hr:write
Calls: PATCH /v1/hr/role-changes/{id}/reject
Example prompt: Reject role change rc_xyz: out of band.

Arguments

Field	Type	Required	Description
`id`	`string`	Yes
`reason`	`string`	Yes

Request HR role changes

Changes data

atlas_hr_role_changes_request

File a new role-change request for an employee (new job title, optional department / location / manager). Lands in PENDING.

Scope: hr:write
Calls: POST /v1/hr/role-changes
Example prompt: File a role change for emp_abc to Senior Engineer effective 1 Aug.

Arguments

Field	Type	Required	Description
`employeeId`	`string`	Yes
`newJobTitle`	`string`	Yes	Target job title for the employee.
`newDepartmentId`	`string`	No
`newLocationId`	`string`	No
`newManagerId`	`string`	No
`effectiveFrom`	`string`	Yes	ISO date (YYYY-MM-DD) the role change takes effect.
`reason`	`string`	No

Assign HR tickets

Changes data

atlas_hr_tickets_assign

HR-admin: assign (or unassign) an HR ticket to an HR teammate. Pass assignedToId=null to clear the assignee.

Scope: hr:write
Calls: PATCH /v1/hr/tickets/{id}/assign
Example prompt: Assign HR ticket hrt_xyz to me.

Arguments

Field	Type	Required	Description
`id`	`string`	Yes
`assignedToId`	`string \| null`	Yes	Employee id to assign as the ticket owner. Pass null to unassign.

Close HR tickets

Changes data

atlas_hr_tickets_close

HR-admin: close an HR ticket (sets closedAt). Closed tickets are read-only.

Scope: hr:write
Calls: PATCH /v1/hr/tickets/{id}/close
Example prompt: Close HR ticket hrt_xyz.

Arguments

Field	Type	Required	Description
`id`	`string`	Yes

Get HR tickets

Read only

atlas_hr_tickets_get

HR-admin: fetch a single HR helpdesk ticket by id, including all messages (internal notes inclusive).

Scope: hr:read
Calls: GET /v1/hr/tickets/{id}
Example prompt: Show me HR ticket hrt_xyz.

Arguments

Field	Type	Required	Description
`id`	`string`	Yes

List HR tickets

Read only

atlas_hr_tickets_list

HR-admin: list HR helpdesk tickets across the tenant. Filter by status, category, priority, employee, or assignee.

Scope: hr:read
Calls: GET /v1/hr/tickets
Example prompt: Which HR tickets are still OPEN with URGENT priority?

Arguments

Field	Type	Required
`status`	`"OPEN" \| "IN_PROGRESS" \| "WAITING_ON_EMPLOYEE" \| "RESOLVED" \| "CLOSED"`	No
`category`	`"LEAVE" \| "PAYROLL" \| "BENEFITS" \| "DOCUMENTS" \| "POLICY" \| "IT_ACCESS" \| "OTHER"`	No
`priority`	`"LOW" \| "NORMAL" \| "HIGH" \| "URGENT"`	No
`employeeId`	`string`	No
`assignedToId`	`string`	No
`limit`	`integer`	No

Set HR tickets priority

Changes data

atlas_hr_tickets_priority_set

HR-admin: change the priority (LOW / NORMAL / HIGH / URGENT) on an HR ticket.

Scope: hr:write
Calls: PATCH /v1/hr/tickets/{id}/priority
Example prompt: Bump HR ticket hrt_xyz to URGENT.

Arguments

Field	Type	Required	Description
`id`	`string`	Yes
`priority`	`"LOW" \| "NORMAL" \| "HIGH" \| "URGENT"`	Yes

Reply HR tickets

Changes data

atlas_hr_tickets_reply

HR-admin: post a reply on an HR ticket. Set isInternalNote=true for an HR-only note the employee cannot see.

Scope: hr:write
Calls: POST /v1/hr/tickets/{id}/messages
Example prompt: Post an internal note on HR ticket hrt_xyz: pending payroll review.

Arguments

Field	Type	Required	Description
`id`	`string`	Yes	Ticket id the message belongs to.
`body`	`string`	Yes
`isInternalNote`	`boolean`	No	When true, the message is only visible to HR (not the employee).

Resolve HR tickets

Changes data

atlas_hr_tickets_resolve

HR-admin: mark an HR ticket as RESOLVED (sets resolvedAt). Employees can still reply, which reopens it.

Scope: hr:write
Calls: PATCH /v1/hr/tickets/{id}/resolve
Example prompt: Resolve HR ticket hrt_xyz.

Arguments

Field	Type	Required	Description
`id`	`string`	Yes

Transition HR tickets

Changes data

atlas_hr_tickets_transition

HR-admin: move an HR ticket between workflow states (OPEN, IN_PROGRESS, WAITING_ON_EMPLOYEE, RESOLVED, CLOSED).

Scope: hr:write
Calls: PATCH /v1/hr/tickets/{id}/status
Example prompt: Move HR ticket hrt_xyz to IN_PROGRESS.

Arguments

Field	Type	Required	Description
`id`	`string`	Yes
`status`	`"OPEN" \| "IN_PROGRESS" \| "WAITING_ON_EMPLOYEE" \| "RESOLVED" \| "CLOSED"`	Yes