Related Servers

The toolset is mechanically derived from HTTP routes, so the verb often lies: 'create_items_batch_get', 'create_tags_rename', 'create_genres_rename', 'create_authorize', 'create_session_by_id_close' and 'create_watcher_update' are all reads or non-creates exposed under a 'create_' prefix. Several pairs sit adjacently with near-identical names ('get_me_progress_by_id_by_episode_id' vs 'get_me_progress_by_id_remove_from_continue_listening'), and multi-step batch endpoints (batch/scan, batch/update, batch/quickmatch) overlap heavily. An agent would frequently pick the wrong tool or need to consult the route string to disambiguate.

Names are uniformly snake_case and follow a recognizable verb_resource_by_id_path-param pattern, and the list_/get_ split for collections vs. singles is coherent. However the verb is chosen from the HTTP method rather than the action, so 'create_X' covers gets, renames, applies and deletes, and side-effecting GETs like 'get_backups_by_id_apply' read as pure reads. The convention is readable but semantically unreliable.

212 tools is far beyond any reasonable agent-facing surface and is essentially a 1:1 dump of the REST API, including trivial variants (cover, download, track, ffprobe, ebook/status). Most of these would be composed by a handful of higher-level tools, and the sheer count makes selection and context management impractical.

Coverage of the Audiobookshelf domain is broad — items, libraries, collections, playlists, podcasts/episodes, series, authors, users, sessions, backups, notifications, feeds, search, stats and tools — with CRUD on most resources. The main gap is that nearly every description tells the agent to 'read the matching GET or the /schema endpoint' but no schema tool is exposed, leaving payload shapes undiscoverable; a handful of mutations are oddly modeled as GETs.