MCP server for Cisco ACI (Application Centric Infrastructure) network automation with 50 GET and POST operations for complete network automation workflows
Critical deficiencies across all 23 tools. All tools use identical, overly generic parameter schema (query_params: object, optional, no description of what parameters are valid). Descriptions are minimal (10-15 chars) and fail to explain WHEN to use each tool or what distinguishes similar tools (e.g., aci_tenants_get vs aci_application_profiles_get). No output schemas documented. No error handling guidance. Parameter descriptions are absent. Tools lack verb-noun clarity (e.g., 'aci_tenants_get' is acceptable but 'aci_simple_test' is vague). Two write tools (aci_tenant_create, aci_vrf_create) have slightly better schemas but still lack output documentation and error recovery guidance.
Get all application profiles from ACI
Get all bridge domains from ACI
Get all contexts (VRFs) from ACI
Get all contract subjects from ACI
Get all contracts from ACI
Get critical faults from ACI
Get all physical domains from ACI
All 21 GET tools use identical, undocumented query_params parameter (type: object, optional, no description). LLMs cannot determine what query parameters are valid (filter, limit, offset, etc.). Violates pattern:constrained-input and pattern:tool-description.
No output schemas documented for any tool. LLMs cannot plan downstream calls or extract required fields (e.g., tenant_id, vrf_id). Violates pattern:tool and pattern:response-shaper.
Inferred effective spec: <=2025-11-25.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 38 | <=2025-11-25 | v2 |
Get all endpoint groups (EPGs) from ACI
Get all endpoints from ACI
Get all ethernet interfaces from ACI
Get fabric health from ACI
Get fabric links from ACI
Get all fabric nodes from ACI
Get all faults from ACI
Get all filter entries from ACI
Get all filters from ACI
Get all physical interfaces from ACI
Simple test tool for ACI connectivity
Get all subnets from ACI
Create a new tenant in ACI
Get all tenants from ACI
Get all VLAN pools from ACI
Create a new VRF (Context) in ACI
Descriptions are 10-25 characters, below the 34-char p10 baseline. Descriptions like 'Get all tenants from ACI' lack context for LLM selection: when to use this vs aci_application_profiles_get? What does the response contain? Violates pattern:tool-description.
No error handling guidance. Code returns generic error dicts with 'error' and 'status' fields, but no recovery hints. If authentication fails or API returns 404, LLM has no guidance on what to do next. Violates pattern:recovery-guide.
No pagination support visible. GET tools accept query_params but do not document limit/offset/page parameters or return total_count/next_cursor. Large result sets will blow context window. Violates pattern:paginated-result.