Related Servers

There is heavy functional overlap: item reads exist three ways (authoring-get-item, item-service-get-item, provider-get-item), item creation and deletion twice, media upload twice (authoring-upload-media vs media-upload), publishing twice, index rebuild twice, item search four ways, and two nearly identical site-listing tools. To their credit, the descriptions explicitly rank which tool to prefer for each case, which rescues the set from confusion, but the boundaries still require reading long descriptions to resolve.

A strong surface-area prefix convention (authoring-, item-service-, security-, presentation-, common-, indexing-, media-, query-, introspection-) makes grouping readable, and names are consistently kebab-case. However, the verb vocabulary drifts by surface: 'new' (security-new-user) vs 'create' (authoring-create-item), 'remove' vs 'delete', and 'add'/'set' used inconsistently for the same action across groups.

121 tools is far beyond a manageable set and overlaps directly with the redundancy noted above — three item getters, two creators, two deleters, two media uploaders. The Sitecore domain is genuinely large, which explains some breadth, but the count is well past the point where an agent can select reliably without substantial description reading.

Coverage is exhaustive across the domain: full item CRUD plus copy/move/rename, templates, media, users/roles/domains, ACLs and item locks, publishing with status polling, indexing, jobs, workflow history, presentation/layout authoring, and schema introspection. There is no obvious lifecycle gap an agent would hit a dead end on.