Related Servers

Tools are mostly distinct by resource (server, egg, user, node, allocation), with clear admin vs client separation in descriptions. Minor overlap exists between list_server_databases and list_client_databases (though one is referenced but not present), and between get_server and get_server_resources (but descriptions clarify purpose).

All tool names follow a strict verb_noun_concrete pattern (e.g., list_servers, get_server, update_server_build, delete_egg_variable). Variants like update_server_build and update_server_details are consistent and descriptive. No camelCase or inconsistent verbs.

34 tools is on the heavy side but appropriate for a full Pterodactyl panel admin API covering servers, users, eggs, nests, nodes, allocations, and mounts. Each tool maps to a concrete endpoint, and the count is justified by the breadth of the domain, though slightly above the ideal 3-15 range.

Core lifecycle operations are present for servers (create, delete, update details/build/startup, suspend/unsuspend/reinstall), users (create, get, list, update), eggs (list, get, create, update variable, delete, import/export). However, missing operations like get_allocation, get_mount, list_role_permissions, and client-level tools (start/stop, file management) create notable gaps for a fully rounded panel management surface.