Workload

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

5 tools

Calculate workload

Read only

atlas_workload_calculate

Compute per-user, per-day workload allocation for a date window, optionally narrowed by user or project. Returns capacity minutes, allocated minutes, and utilization inputs used by the planner heatmap.

Scope: workload:read
Calls: GET /v1/workload
Example prompt: Compute workload for next week and show capacity vs allocation.

Arguments

Field	Type	Required	Description
`from`	`string`	Yes	Inclusive start date in YYYY-MM-DD format.
`to`	`string`	Yes	Inclusive end date in YYYY-MM-DD format.
`userId`	`string`	No
`projectId`	`string`	No

List workload capacity

Read only

atlas_workload_capacity_list

List configured capacity rows for the tenant so agents can explain workload math and identify missing or stale capacity assumptions. Returns one page at a time; pass the nextCursor of a page as cursor to read the next one.

Scope: workload:read
Calls: GET /v1/workload/capacity
Example prompt: Show configured weekly capacity for the team.

Arguments

Field	Type	Required	Description
`limit`	`integer`	No	How many rows to return, 1 to 100. 50 by default.
`cursor`	`string`	No	The nextCursor of the previous page. Leave it out for the first page.
`sort`	`"updatedAt" \| "createdAt" \| "effectiveFrom"`	No	The field to sort on: updatedAt, createdAt, effectiveFrom. updatedAt by default.
`order`	`"asc" \| "desc"`	No	asc or desc. desc by default.

Set workload capacity

Changes data

atlas_workload_capacity_set

Create or replace one user capacity profile with seven weekday hour values, a timezone, and optional effective-from date. Idempotent per MCP call.

Scope: workload:write
Calls: POST /v1/workload/capacity
Example prompt: Set usr_123 capacity to 8,8,8,8,6,0,0 hours in Asia/Kolkata.

Arguments

Field	Type	Required
`userId`	`string`	Yes
`hoursPerWeekday`	`array of number`	Yes
`timezone`	`string`	No
`effectiveFrom`	`string`	No

List workload day tasks

Read only

atlas_workload_day_tasks_list

List the tasks that contribute to one user-day workload cell, optionally filtered to a project. Use this to explain why a person is overloaded on a specific day.

Scope: workload:read
Calls: GET /v1/workload/users/{userId}/days/{date}/tasks
Example prompt: Why is usr_123 overloaded on 2026-06-10?

Arguments

Field	Type	Required
`userId`	`string`	Yes
`date`	`string`	Yes
`projectId`	`string`	No

List workload overallocations

Read only

atlas_workload_overallocations_list

List only overloaded user-days for a date window, including overage minutes, utilization percentage, and severity so an agent can prioritize capacity interventions.

Scope: workload:read
Calls: GET /v1/workload/overallocations
Example prompt: Who is overallocated this sprint and how severe is it?

Arguments

Field	Type	Required	Description
`from`	`string`	Yes	Inclusive start date in YYYY-MM-DD format.
`to`	`string`	Yes	Inclusive end date in YYYY-MM-DD format.
`userId`	`string`	No
`projectId`	`string`	No

Workload

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

5 tools

Calculate workload

Read only

atlas_workload_calculate

Scope: workload:read
Calls: GET /v1/workload
Example prompt: Compute workload for next week and show capacity vs allocation.

Arguments

Field	Type	Required	Description
`from`	`string`	Yes	Inclusive start date in YYYY-MM-DD format.
`to`	`string`	Yes	Inclusive end date in YYYY-MM-DD format.
`userId`	`string`	No
`projectId`	`string`	No

List workload capacity

Read only

atlas_workload_capacity_list

Scope: workload:read
Calls: GET /v1/workload/capacity
Example prompt: Show configured weekly capacity for the team.

Arguments

Field	Type	Required	Description
`limit`	`integer`	No	How many rows to return, 1 to 100. 50 by default.
`cursor`	`string`	No	The nextCursor of the previous page. Leave it out for the first page.
`sort`	`"updatedAt" \| "createdAt" \| "effectiveFrom"`	No	The field to sort on: updatedAt, createdAt, effectiveFrom. updatedAt by default.
`order`	`"asc" \| "desc"`	No	asc or desc. desc by default.

Set workload capacity

Changes data

atlas_workload_capacity_set

Create or replace one user capacity profile with seven weekday hour values, a timezone, and optional effective-from date. Idempotent per MCP call.

Scope: workload:write
Calls: POST /v1/workload/capacity
Example prompt: Set usr_123 capacity to 8,8,8,8,6,0,0 hours in Asia/Kolkata.

Arguments

Field	Type	Required
`userId`	`string`	Yes
`hoursPerWeekday`	`array of number`	Yes
`timezone`	`string`	No
`effectiveFrom`	`string`	No

List workload day tasks

Read only

atlas_workload_day_tasks_list

List the tasks that contribute to one user-day workload cell, optionally filtered to a project. Use this to explain why a person is overloaded on a specific day.

Scope: workload:read
Calls: GET /v1/workload/users/{userId}/days/{date}/tasks
Example prompt: Why is usr_123 overloaded on 2026-06-10?

Arguments

Field	Type	Required
`userId`	`string`	Yes
`date`	`string`	Yes
`projectId`	`string`	No

List workload overallocations

Read only

atlas_workload_overallocations_list

List only overloaded user-days for a date window, including overage minutes, utilization percentage, and severity so an agent can prioritize capacity interventions.

Scope: workload:read
Calls: GET /v1/workload/overallocations
Example prompt: Who is overallocated this sprint and how severe is it?

Arguments

Field	Type	Required	Description
`from`	`string`	Yes	Inclusive start date in YYYY-MM-DD format.
`to`	`string`	Yes	Inclusive end date in YYYY-MM-DD format.
`userId`	`string`	No
`projectId`	`string`	No