Skip to main content
Glama

pingwa

by io.github.grzgrzgrz3

ask

Ask the human a question on WhatsApp and BLOCK until they reply (or timeout).

    `text` is the question. `buttons` (optional, up to 3) render as tappable reply
    buttons; omit them to invite a free-text answer the human types on their phone —
    use this to let the human steer you mid-task. `timeout` is seconds to wait
    (max 90). Returns the human's reply (free text and/or the chosen option). On
    timeout, returns a note — the question was delivered and the answer is still
    retrievable via `check_replies`.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
textYes
buttonsNo
timeoutNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

TDQS

A5/5.0
Behavior5/5

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

With no annotations, the description fully covers behavior: blocking until reply or timeout, buttons optional, timeout max 90, return on timeout is a note with retrievable answer. No destructive behavior is implied, but the blocking nature is clearly disclosed.

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?

Description is two paragraphs with clear structure: first sentence defines purpose, then bullet-like explanations of parameters and timeout handling. Backticks for parameter names aid readability. No unnecessary words; every sentence adds value.

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 existence of an output schema (not shown), the description needn't detail return values. It covers the blocking behavior, optional buttons, timeout handling, and how to retrieve answers on timeout. This is complete for the tool's complexity.

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?

Schema coverage is 0%, so description must explain parameters. It defines text as 'the question,' buttons as 'optional up to 3 tappable reply buttons; omit for free-text,' and timeout as 'seconds to wait (max 90).' This adds complete meaning beyond the schema's minimal type info.

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?

Description clearly states 'Ask the human a question on WhatsApp and BLOCK until they reply (or timeout).' It specifies the verb (ask), resource (human on WhatsApp), and blocking behavior. It distinguishes from sibling check_replies by mentioning that timeout replies are retrievable via that tool.

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

Usage Guidelines5/5

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

The description explains when to use this tool (when you need a question answered), optional buttons vs free-text, timeout limits (max 90 seconds), and directs to check_replies for retrieving answers on timeout. This provides clear guidance on alternatives.

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