Related Servers

Tools are grouped by domain (Sheets, Drive, Docs, ATS, notes) and within each group target distinct operations: read vs. append vs. update vs. insert for sheets, and fetch vs. sweep vs. check for ATS. The only mild overlap is between ats_check_board and check_posting, but descriptions clearly separate board-level from URL-level checks. Overall an agent can reliably select the right tool.

Most tools follow a verb_noun pattern, with domain prefixes for larger clusters (drive_*, docs_*, ats_*) and bare verb_noun names for notes and HTTP (save_note, list_notes, search_notes). The pattern is predictable and consistent within each domain. The main exception is http_request, which is a noun phrase rather than verb_noun, but it's a generic utility rather than a domain operation.

At 27 tools, the surface is large, but it is justified by covering five distinct domains (Sheets, Drive, Docs, ATS, notes) plus a generic HTTP client. Each tool addresses a specific need within its domain, so none feels redundant. It is slightly dense but not bloated relative to the server's stated 'toolkit' purpose.

Sheets, Drive, and Docs each have solid CRUD-like coverage: read/append/update/insert for sheets, read/append/replace for Docs, and update/move/rename/trash/sync for Drive. The ATS tools are notably thorough, covering fetch, sweep, check, and form inspection. Minor gaps include no create-doc/create-sheet tool (though sync can upload files) and no board submission, but these are reasonable omissions for a read/update-oriented toolkit.