kweenkl MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| KWEENKL_DEBUG | No | Enable debug logging (set to 'true') | |
| KWEENKL_API_URL | No | API base URL | https://api.kweenkl.com |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| kweenklB | Send a push notification using kweenkl. The verb 'kweenkl' means to send a notification. Use this to notify users about important events, updates, or information that requires immediate attention. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
With only one tool, there is no possibility of ambiguity or overlap between tools, as there are no other tools to confuse it with. The tool's purpose is clearly defined as sending push notifications, leaving no room for misselection.
The single tool name 'kweenkl' follows a consistent pattern by default, as there are no other tools to compare it against. There is no mixing of conventions or deviations, making it perfectly consistent within the set.
A single tool is generally too few for most server purposes, as it limits functionality and scope. While it might suffice for a minimal notification service, it feels thin and lacks the depth typically expected for a coherent tool set, making it borderline inappropriate.
The tool covers the core action of sending notifications, but there are notable gaps in the lifecycle, such as managing notifications (e.g., listing, updating, or deleting them). The surface is incomplete for a full notification system, though agents might work around this for basic use cases.