MCP server for Webex integration, enabling management of spaces, messaging, and meeting creation
Server has 3 tools with explicit Zod schemas and basic descriptions, but suffers from critical issues: (1) webex_send_message_to_space has a severely misleading parameter description ('The URL of the image to show' for spaceId), (2) descriptions are too brief (10-30 chars) to guide LLM tool selection, (3) no output schemas documented, (4) no error recovery guidance, (5) no parameter constraints (enums, ranges, formats). Tools are registered with names and schemas visible, but quality is well below production baseline.
Create a Webex meeting
List Webex spaces
Send a message to a Webex space
webex_send_message_to_space spaceId parameter has incorrect description: 'The URL of the image to show' instead of describing the space/room ID. This will confuse LLMs about what value to pass.
All tool descriptions are 10-30 characters, far below the 194-char baseline for production tools. Descriptions lack WHEN to use, WHAT it returns, and prerequisites. LLMs cannot reliably select tools with such minimal context.
No output schemas documented. Callers cannot know what fields to expect from responses. webex_list_spaces returns text content, webex_send_message_to_space returns confirmation text, webex_create_meeting returns meeting ID, but none are formally specified.
Inferred effective spec: <=2025-11-25.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 40 | <=2025-11-25 | v2 |
No parameter constraints. startTime and endTime in webex_create_meeting lack format specification (ISO 8601?). No validation that endTime > startTime. No enum for markdown vs text vs adaptiveCard in webex_send_message_to_space.
Error handling is minimal. All failures throw generic UserError('Failed to...'). No guidance on retry, no indication of which errors are transient vs permanent, no suggestions for recovery (e.g., 'Try list_spaces first to find a valid spaceId').