Skip to main content
Glama
@jabee/mcp

@jabee/mcp

by MumenTayyem

Ask a person to approve something on WhatsApp

ask_person

Sends a WhatsApp approval request to a named person before expensive or irreversible actions, then waits for their approval, rejection, or amendment.

Instructions

Ask a named person to approve, reject or amend something, on WhatsApp, and wait for their answer. Use this before doing anything that is expensive or impossible to undo: issuing a refund, sending a quote, posting publicly, emailing a list, deleting data. The person gets buttons on their phone and can also reply with free text to amend what you proposed. Returns their decision, or the request id if nobody has answered yet.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "title": "<title>"
    },
    "name": "ask_person"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlNoA link to the thing being decided.
bodyNoWhy you are asking, and anything they need in order to decide.
titleYesThe decision, in one line. 'Refund AED 450 to Sara'.
external_idNoYour own id for the thing being decided. Sending the same one twice returns the existing request rather than asking a second time, so a retry is safe.
wait_secondsNoHow long to wait for an answer before returning. Defaults to 120. Pass 0 to return immediately and poll with check_approval.
allow_amendmentNoOffer an Edit button that asks for free text. Use it when the answer could reasonably be 'yes but change this' rather than only yes or no.
expires_in_minutesNoHow long the decision stays useful. Defaults to a day.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.3

TDQS

A4.5/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and mostly succeeds: it discloses that the call blocks waiting for an answer, that the recipient sees buttons plus a free-text amendment path, and what is returned on timeout ('the request id if nobody has answered yet'). It does not mention authorization prerequisites (does the person need a WhatsApp account configured?) or rate/throughput limits.

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?

Three sentences, front-loaded with the action, then the trigger conditions, then the return behavior. Every clause carries information and nothing is repeated from the schema.

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?

There is no output schema, so the description must describe returns, and it does ('their decision, or the request id if nobody has answered yet'). Combined with the fully documented 7-parameter schema, an agent has enough to call this correctly on the first attempt.

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

Parameters4/5

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

Schema coverage is already 100%, so 3 is the baseline; the description earns slightly more by explaining the amendment round-trip that motivates allow_amendment, and by framing the wait-then-poll lifecycle. It still adds nothing about expires_in_minutes, external_id idempotency, or url beyond what the schema text already states.

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 opens with a precise verb-plus-resource statement ('Ask a named person to approve, reject or amend something, on WhatsApp, and wait for their answer'), covering the channel and the blocking behavior in one line. An agent can immediately tell this is a human-in-the-loop approval call rather than a notification (tell_person) or a status read (check_approval).

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?

It gives a concrete trigger rule and backs it with examples: 'Use this before doing anything that is expensive or impossible to undo: issuing a refund, sending a quote, posting publicly, emailing a list, deleting data.' What is missing is explicit routing to the siblings — it never says when to use check_approval instead of waiting, or tell_person instead of asking.

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

Deploy Server

Other Tools