MCP server for WardenPoint: let an agent configure recipients, groups, escalation policies, on-call schedules and alert routing. Built entirely from the installation's own OpenAPI description.
WardenPoint MCP exposes 9 tools with basic schemas and descriptions. All tools have non-empty descriptions (10 - 200 chars, within baseline range). Input schemas are present for all tools, but most are minimal: 6 tools accept only simple string/UUID parameters with no nested structure; 3 tools accept a generic 'body' object with type 'object' but no schema detail. Parameter descriptions are present and specific (e.g., 'The UUID of the recipient'). However, critical gaps emerge: (1) No output schemas documented, LLMs cannot predict response structure for chaining; (2) No error handling guidance, tools return raw API errors with no recovery hints; (3) Generic 'body' parameters lack schema constraints, forcing LLMs to guess JSON structure; (4) No pagination support declared despite operating on collections (recipients, integrations); (5) Tool names are REST-style (v1_recipients_index) rather than action-verb style (list_recipients), reducing clarity. The server is functional but below production baseline for agent composition.
List the capabilities of the WardenPoint installation and the account's current state.
Post an alert to an observability integration.
Delete an observability integration.
Create a new observability integration.
Add a contact to a recipient.
Delete a recipient.
No output schemas documented. LLMs cannot predict response structure, breaking tool chaining and forcing discovery calls.
Generic 'body' parameters (v1_recipients_store, v1_recipient_contacts_store, v1_observability_integrations_store, v1_integration_alerts_store) lack schema constraints. LLMs must guess JSON structure.
Tool names use REST-style (v1_recipients_index, v1_recipients_store) instead of action verbs (list_recipients, create_recipient). Reduces LLM clarity on intent.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | D | 52 | 2026-07-28+ | v2 |
List all recipients in the account.
Retrieve a specific recipient by UUID.
Create a new recipient.
No error handling guidance. Tools return raw API errors with no recovery hints (e.g., 'User not found. Try search_users() first.').
No pagination support declared for collection tools (v1_recipients_index, v1_capabilities_index). Large result sets risk context window exhaustion.