Skip to main content
Glama

pingwa

by io.github.grzgrzgrz3

notify

Send a WhatsApp notification to the account owner's own phone.

    `text` is the message (1-1024 chars). `image_url` (optional) is a public https
    image link — a screenshot, chart or diff — delivered as an image with `text` as
    the caption when the user's 24h window is open (otherwise text only). Returns a
    confirmation with the queued message id; raises an actionable error on quota/auth.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
textYes
image_urlNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

TDQS

A4.8/5.0
Behavior5/5

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

With no annotations, the description fully explains behavior: how image_url works conditionally (24h window), the return value (confirmation with queued message id), and error handling (actionable error on quota/auth). This is thorough.

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?

The description is concise, front-loads the purpose, and efficiently covers parameters, behavior, and return values in a single paragraph with no redundant information.

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

Completeness5/5

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

Given the low parameter count and presence of an output schema, the description is complete. It covers all necessary aspects for an agent to use the tool correctly, including error scenarios.

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

Parameters5/5

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

Despite 0% schema coverage from context signals, the description provides rich semantics for both parameters: text limits (1-1024 chars) and image_url usage (public https, conditional image delivery). This adds significant value beyond the schema.

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 the tool sends a WhatsApp notification to the account owner's own phone, specifying the verb 'send' and the resource 'WhatsApp notification'. It distinguishes from siblings like 'ask' and 'check_replies' which serve different purposes.

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?

The description implies usage for self-notification and explains image behavior, but does not explicitly state when to use versus alternatives or when not to use. The context is clear, leaving no exclusion guidance.

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

All pingwa 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

A4.4/5.0
Disambiguation4/5

Tools are mostly distinct: ask (blocking question), check_replies (retrieve messages), notify (send notification), check_status (account info), upgrade (plan management). There is some overlap between ask and check_replies, but descriptions clarify their different purposes.

Naming Consistency5/5

All tool names are single lowercase verbs, following a consistent verb-only naming pattern. No mixing of conventions.

Tool Count5/5

Five tools is appropriate for the server's purpose of WhatsApp interaction, covering core actions without being excessive or too sparse.

Completeness4/5

The tool set covers key operations: asking questions, retrieving replies, sending notifications, checking status, and upgrading. Minor gaps exist (e.g., no separate send image tool), but the core workflow is supported.

Resources