Related Servers

The four surface prefixes (ers/openapi/mnt/dc) plus routing guidance (ise_route, ise_capabilities) make the tool families distinguishable, and typed tools name their resources clearly. However, generic tools (ise_ers_list, ise_dc_view, ise_openapi_request, ise_mnt_request) overlap substantially with the typed wrappers they subsume, and pairs like ise_mnt_session_by_ip vs ise_mnt_session_by_endpoint_ip or the three RADIUS authentication DC views require careful reading to disambiguate.

Tool names follow a systematic family-prefix scheme (ise_ers_, ise_openapi_, ise_mnt_, ise_dc_) with mostly consistent verb_noun structure within each family. Minor deviations exist: OpenAPI mixes ordering (ise_openapi_radius_dictionary_list vs ise_openapi_radius_policy_set_list), MNT session tools use irregular forms (session_by_mac vs active_session_list), and DC view suffixes (_week, _summary) are not uniform.

At 201 tools this is far beyond the 'too many' threshold and will heavily burden an agent's context window and selection speed. The count is inflated by redundancy: generic tools (ise_ers_list/get/create/update/delete, ise_dc_view, ise_dc_query, raw passthroughs) already subsume most of the ~60 typed ERS wrappers and ~15 typed DC view wrappers. The breadth is genuine — four API surfaces, dozens of resource types — which keeps it from a 1, but the surface is clearly over-tooled.

The server covers all four Cisco ISE API surfaces with near-complete lifecycle coverage for ERS resources, broad Open API coverage (policy, certs, backup, licensing, patches, deployment), and rich Data Connect/Monitor reporting. Minor gaps exist — no typed update/delete for RADIUS/TACACS authentication/authorization rules, and some operations reachable only via raw passthrough — but the generic CRUD/request/query tools and deployment-registry tools make workarounds straightforward.