Tool reference

Tools below are listed by domain. The set you actually see is filtered by your API key's permissions — tools/list returns only the tools your role can call.

Organisation

Tool	What it does
`get_organization`	Details about the current org.
`list_members`	All members and their roles.
`org_snapshot`	Compact multi-domain snapshot — headcount, leave usage YTD, latest payroll runs, active performance cycle. Prefer this over four list calls.

People (CoreHR)

Tool	What it does
`list_employees`	List employees, with optional search/department/status filters.
`get_employee`	Full employee profile by ID.
`create_employee`	Create a new employee. Requires `employee.manage`.
`list_departments`	All departments in the org.

Leave

Tool	What it does
`list_leave_types`	Available leave types.
`get_leave_balances`	Balances for an employee in a leave year.
`submit_leave_request`	Submit a leave request for an employee.
`list_leave_requests`	List requests, filterable by employee/department/type/status/date range.
`leave_by_department`	Aggregate leave usage by department for a date range. Cheaper than listing all employees when you want a team breakdown.

Payroll

Tool	What it does
`list_payroll_runs`	All payroll runs — name, status, period, totals, headcount.
`get_payroll_run_summary`	Per-employee breakdown of a run: basic salary, gross, net, deductions, benefits, employer cost, computation trace.
`simulate_employee_payroll`	Simulate a payroll computation for one employee using current org config. No run is created.
`list_benefits`	Configured benefits and allowances.
`list_deductions`	Configured statutory and custom deductions.

Calling conventions

All tool inputs are JSON objects. Each tool's schema is returned by tools/list, so an agent does not need to be told the shape ahead of time.
Money fields are decimal numbers, currency is the org default.
Dates are ISO-8601.
Errors come back as JSON-RPC errors with the same code / message / details shape as the REST API.

Adding tools

The tool set evolves alongside the REST API. New tools follow the same rule: they're surfaced if — and only if — a regular API key with the right permissions could perform the underlying action.