Related Servers

Most tools have a clear resource+action target, and the long descriptions actively disambiguate near-neighbours (get_feedback vs get_feedback_status, get_request vs get_my_requests). A few clusters remain genuinely confusable: get_team / get_team_snapshot / get_org_chart all describe 'people around you', and get_worker / get_my_profile / get_worker_task form a layered trio an agent must reason through. The generic escape hatches (fetch, graphql, get_task) also require judgment about which to reach for.

All tools use a uniform workday_ prefix with snake_case and a verb_noun shape (get_, update_, run_, open_, give_, request_). The only deviations are the noun-only helpers workday_healthcheck, workday_fetch and workday_graphql, which drop the verb but are still readable and clearly signposted as infrastructure. No mixed camelCase/snake_case chaos.

27 tools is at the heavy end, though Workday is an enormous domain (feedback, reviews, benefits, reports, inbox, org data) so each area legitimately needs coverage. Still, there is measurable layering overhead: three generic escape hatches, three team/org readers, and two profile readers could likely be consolidated. The surface feels broad rather than bloated, but it is past comfortable.

Read coverage is strong across profiles, feedback, reviews, benefits, reports, dashboards and inbox, and four write tools cover feedback, requests and benefits enrollment. However the server is explicitly read-only on nearly everything else: the inbox lists approvals and tasks but there is no way to approve, decline or act on them, no time-off or time-entry operations, no profile update, and no way to withdraw a feedback request. Agents hitting those workflows dead-end and must fall back to raw fetch/graphql.