No user-submitted related servers found.
Scored across 242 tools
Every tool embeds its entity and operation in the name (list_workflows, update_agent, restore_flow_version), so selection is unambiguous even across 242 tools. Potentially confusable clusters like execute_tool vs dry_run_tool vs execute_stored_connector and restore_X vs restore_X_version vs restore_deleted_X_version are explicitly differentiated in their descriptions. No two tools appear to do the same thing.
The set follows a rigid snake_case verb_noun pattern: list_/read_/create_/update_/delete_/restore_/request_publish_/discard_*_draft, with version operations consistently suffixed (_versions, _version, _published) and list tools pluralized. The single non-verb outlier, axonity_conventions, is a deliberate read-me-first marker rather than a genuine pattern break.
At 242 tools, the surface is far beyond even the 16-25 'heavy' band and sits in the extreme-mismatch territory. The count is inflated by repeating an identical ~18-tool lifecycle template across ten-plus entity types, which could have been compressed into parameterized entity operations. The systematic repetition makes it navigable, but the selection burden on an agent is severe.
Coverage of the draft→publish lifecycle is exceptionally thorough: every entity has CRUD, soft-delete/restore, deleted-list, draft discard, publish approval, full version history (including deleted-version recovery and major-version naming), and published-read variants, plus run, trigger, prompt-stack, and wiring tools. Minor gaps remain: cron and webhook triggers have no update operation (only conditional triggers do), and there is no way to cancel or withdraw a pending publish approval.