Model Context Protocol server that provides network automation tools for interacting with Cisco NSO via RESTCONF
The server has 9 tools with consistent naming (verb_noun pattern) and tool annotations. However, critical gaps emerge: most tools lack visible input schemas in the provided code (only 2 of 9 show complete schemas), parameter descriptions are brief and generic, and output schemas are entirely undocumented. Error handling returns unstructured text without recovery guidance. The code shows basic structure but falls short of production-grade definition quality, descriptions are present but minimal (10-50 chars typical), and schema visibility is incomplete.
Check the sync status for a specific device in Cisco NSO. Requires a 'device_name' parameter.
Retrieve the full configuration for a specific device in Cisco NSO. Requires a 'device_name' parameter.
Retrieve the available device groups in Cisco NSO.
Retrieve the available Network Element Driver (NED) IDs in Cisco NSO.
Retrieve platform information for a specific device in Cisco NSO. Requires a 'device_name' parameter.
Retrieve the state for a specific device in Cisco NSO. Requires a 'device_name' parameter.
Output schemas completely absent across all 9 tools. LLMs cannot reason about returned fields, plan chained calls, or extract data reliably.
No input schemas visible for 4 tools (get_service_types, get_device_groups, get_device_ned_ids, and inferred parameter lists).
Descriptions are 10 - 70 characters, below the 50-200 char production baseline. Too brief to guide LLM selection. Example: 'Retrieve the available service types in Cisco NSO.' (48 chars) omits when to call it or what it returns.
Inferred effective spec: <=2025-11-25.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-22 | D | 51 | <=2025-11-25 | v2 |
| 2026-03-09 | F | 0 | - | v1 |
Retrieve the available service types in Cisco NSO.
Retrieve the available services in Cisco NSO. Requires a 'service_type' parameter.
Sync from a specific device in Cisco NSO. Requires a 'device_name' parameter.
sync_from_device is a WRITE operation but its description does not declare this. Error handling returns unstructured error text without recovery steps. No dry-run or confirmation pattern for destructive intent.
All error responses return {"status": "error", "error_message": "..."} with no actionable recovery guidance. LLM cannot distinguish retryable errors, user-fixable errors, or fatal ones.
Parameter descriptions are generic or missing. Example: get_device_config's 'device_name' param description is 'The name of the device for which to retrieve configuration' (11 words). No guidance on format, case sensitivity, or how to obtain valid names.
No pagination support visible. List tools (get_services, get_device_groups, get_device_ned_ids) lack limit/offset/page parameters and total count in response. Large results risk context window exhaustion.
No input validation shown in handler code. Handlers check for required params but do not validate format, enum constraints, or range. Invalid inputs return generic errors instead of actionable feedback.