Skip to main content
Glama

kweenkl-mcp

by io.github.antoinedelorme

kweenkl

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.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
titleNoOptional title for the notification. Should be brief (max 50 chars recommended). If omitted, only the message will be shown.
glanceNoOptional structured visualization rendered as a card inside the kweenkl iOS app. Must include a 'type' field. v1 supports type='line_chart' with required fields {labels: string[], values: number[]} (same length, ≥2 points) and optional fields {subtitle, accent (#hex), comment, x_label, y_label}. Example: {type:'line_chart', subtitle:'Évolution 2015→2024', labels:['2015','2016','2017'], values:[670,720,780], accent:'#ff6b6b', comment:'tendance haussière'}
messageYesThe notification message content. Should be clear, concise, and actionable. Maximum recommended length: 500 characters for optimal mobile display.
payloadNoOptional custom JSON payload for additional metadata. Can include any structured data that your app might process (e.g., action buttons, deep links, custom data).
priorityNoPriority level for the notification. 'high' = urgent/critical alerts, 'normal' = standard updates (default), 'low' = non-urgent information.
webhook_tokenYesThe webhook token for your kweenkl channel. Format: UUID-like string. Can be found in the kweenkl iOS app by opening a channel and viewing 'Channel Info'.

TDQS

A3.9/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already indicate readOnlyHint=false, destructiveHint=false. The description adds that notifications are for 'important events' but does not disclose any additional behavioral traits (e.g., rate limits, delivery guarantees).

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two concise sentences: one for action, one for usage guidance. No redundant or fluff content.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Despite complexity (6 params, nested glance object), the description is minimal. It does not mention the kweenkl platform dependency, the requirement for a webhook token, or the glance card visualization. The schema covers details, but the description lacks overarching context.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% with detailed descriptions for each parameter. The description text adds no extra meaning beyond the schema, so baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states 'Send a push notification using kweenkl' and explicitly defines the verb meaning. It distinguishes from siblings like 'fetch' and 'search' which are unrelated.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Describes when to use: 'notify users about important events, updates, or information that requires immediate attention.' Does not provide explicit exclusions or alternatives, but sibling names imply distinct purposes.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All kweenkl-mcp toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.7/5.0
Disambiguation5/5

Each tool has a clearly distinct purpose: fetch retrieves by ID, kweenkl sends notifications, login and login_check handle auth, status checks connectivity, and search queries history. No ambiguity.

Naming Consistency3/5

Tools mix generic verbs like 'fetch' and 'search' with the 'kweenkl_' prefix for auth and status tools, and 'kweenkl' as a standalone verb tool. This is somewhat inconsistent but still readable.

Tool Count5/5

6 tools is well-scoped for a notification service. Each tool serves a needed function without bloat.

Completeness2/5

Lacks channel management tools (create, update, delete) and a listing tool beyond search. Users cannot fully manage the lifecycle of channels or notifications.

Resources