Related Servers

Every tool has a clearly distinct purpose with no ambiguity. The tools follow a consistent pattern of resource type + action (e.g., create_address, get_address, list_addresses), making it easy to distinguish between different operations on different configuration objects. Even with 151 tools, each serves a specific function in the SCM domain.

All tools follow a perfect scm_verb_noun pattern with snake_case throughout. The naming is exceptionally consistent: scm_create_address, scm_get_address, scm_list_addresses, scm_update_address, scm_delete_address, and this pattern repeats across all resource types. There are no deviations in naming conventions.

With 151 tools, this is an extremely large tool surface that will overwhelm agents and cause selection challenges. While the SCM domain is complex, this many tools represents an excessive granularity that exceeds typical agent-friendly scopes (3-15 tools). The count feels heavy and unmanageable despite the comprehensive coverage.

The tool surface provides complete CRUD/lifecycle coverage for the SCM domain across all major resource types. Every configuration object has create, get, list, update, and delete operations where applicable, plus specialized tools like commit, search, move, and associate/disassociate. There are no obvious gaps in the coverage for firewall configuration management.