Model Context Protocol server for Qlik Cloud API
This server has 29 tools with significant quality gaps. Tool names lack consistent verb-noun structure (e.g., 'handleAppReloadSucceeded' vs 'listContexts'). Descriptions are present but minimal (10-50 chars), providing insufficient context for LLM selection. Input schemas exist but are sparse: most parameters lack type constraints, enums, or validation guidance. Event handler tools (16-29) have generic 'event' object parameters with no schema detail. No output schemas documented. Error handling is absent, no recovery guidance, retryability classification, or actionable error messages. Security concerns: no evidence of permission gates, audit logging, or secret injection patterns. Tool composition shows poor separation of concerns (e.g., notification handlers mixing Slack and email logic). Overall, this reads as an early-stage implementation missing production-grade patterns.
Connect a context to the engine
Create a new context
Create a new object in a context
Delete a context
Delete an object
Disconnect a context from the engine
Execute a method on an object
Get a context by ID
Event handler tools (handleAppReloadSucceeded, handleMaintenanceScheduled, handleUserCreated, etc.) use generic 'event' object parameters with no schema detail. LLMs cannot determine what fields the event object contains or how to construct it.
No output schemas documented for any tool. LLMs cannot plan downstream calls or extract required fields (e.g., context_id after createContext). This violates the documented output schema requirement.
Inferred effective spec: <=2025-11-25.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 38 | <=2025-11-25 | v2 |
Get an object by ID
Get the current state of a context
Handle app deleted event
Handle app published event
Handle app reload failed event
Handle app reload succeeded event
Handle maintenance completed event
Handle maintenance scheduled event
Handle maintenance started event
Handle system alert event
Handle user created event
Handle user deleted event
Handle user login event
Handle user updated event
List all contexts
List all objects in a context
List all saved states for a context
Restore a saved state
Save the current state of a context
Send email notification
Send Slack notification
Descriptions are uniformly minimal (10-50 chars). 'Create a new context' and 'Get a context by ID' lack WHEN to use, prerequisites, or side effects. Baseline for A+ tools is 50-200 chars with actionable guidance.
Event handler naming uses 'handle' prefix (handleAppReloadSucceeded) instead of action verbs (process_app_reload_event, notify_on_app_reload). 'Handle' is generic and does not convey intent to LLMs.
No error handling guidance. Tools lack recovery hints, retryability classification, or actionable error messages. An LLM receiving 'Context not found' has no next step.