Loading ToolBench
MCP server for Alcatel-Lucent Enterprise OmniSwitch AOS8 network devices
8 tools with consistent naming (aos_show_*) and detailed descriptions (150-250 chars each). All tools are READ_ONLY with clear intent. However, input schemas are minimal (only 'host' parameter with basic string type, no format/pattern constraints). Output schemas are completely undocumented, LLMs cannot predict what fields to expect from responses. No parameter descriptions beyond the host field. Error handling and recovery guidance absent. Descriptions are good but lack dependency hints and prerequisites.
Return chassis information for an AOS8 OmniSwitch. Runs ``show chassis`` and returns model name, description, part number, hardware revision, serial number, manufacture date, admin/operational status, reset count and MAC address.
Return OmniVista Cloud Agent status for an OmniSwitch. Runs ``show cloud-agent status`` and returns the admin state, activation and device management states, cloud group, server endpoints (activation, VPN, OV tenant), NTP/DNS server lists, call-home timer and certificate status.
Return Chassis Management Module (CMM) information for an AOS8 OmniSwitch. Runs ``show cmm`` and returns model name, description, part number, hardware revision, serial number, manufacture date, admin/operational status, maximum power consumption, MAC address and FPGA versions.
Return DHCP relay global configuration for an OmniSwitch. Runs ``show ip dhcp relay`` and returns administrative status, forward delay, maximum hops, relay agent information flag, option-82 format and string, PXE support status and relay mode.
Return DHCP relay statistics for an OmniSwitch. Runs ``show ip dhcp relay statistics`` and returns packet counters (total count and delta since last clear) for each statistics category such as client reception, forward-delay violations, relay drops, etc.
Output schemas completely undocumented. Tool descriptions state what fields are returned (e.g., 'returns description, uptime, contact, name, location...') but no structured schema is provided. LLMs cannot plan downstream operations or extract specific fields without guessing.
Input parameter 'host' lacks description and format constraints. No indication of whether it accepts FQDN, IPv4, IPv6, or all three. No validation guidance for LLM.
Inferred effective spec: 2026-07-28+.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | D | 55 | 2026-07-28+ | v2 |
Return microcode package information for an AOS8 OmniSwitch. Runs ``show microcode`` and returns the working and certified directories with package names, releases, sizes and descriptions.
Return running directory information for an AOS8 OmniSwitch. Runs ``show running-directory`` and returns the running CMM, CMM mode, current CMM slot, running configuration, certify/restore status and synchronization status.
Return system identity and uptime for an AOS8 OmniSwitch. Runs ``show system`` and returns description, uptime, contact, name, location, date/time and primary flash availability.
No error handling or recovery guidance. Tool descriptions do not explain what happens on connection failure, authentication error, or invalid host. LLM has no guidance on retry strategy or fallback.
No tool annotations (readOnlyHint, destructiveHint, idempotentHint). While all tools are READ_ONLY, this is not declared in the tool metadata, forcing LLMs to infer safety from descriptions alone.
No pagination or result-limiting guidance. Tools return raw CLI output; no indication of max result size, whether results are paginated, or how to handle large responses.