Skip to main content
Glama
@jabee/mcp

@jabee/mcp

by MumenTayyem

Tell a person something on WhatsApp

tell_person

Send one-way WhatsApp notifications to your own verified phone or team members for alerts such as failed builds, shipped orders, or finished jobs, without waiting for a reply.

Instructions

Send a one-way notification to your own phone on WhatsApp: a build failed, an order shipped, a job finished. This reaches your own verified people, never your customers. Returns once it has been sent; it does not wait for a reply.

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": "tell_person"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlNoA link to the thing.
bodyNoThe detail.
titleYesThe headline, in one line.
external_idNoYour own id, so a retry does not send it twice.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.3

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations supplied, the description carries the load and does well: it discloses the one-way nature, the recipient restriction to verified people, and the non-blocking return ('returns once it has been sent; it does not wait for a reply'). It omits failure behavior, e.g., what happens if a recipient is not verified, and says nothing about rate limits or delivery confirmation.

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 tight sentences, front-loaded with the core action, then scope, then return semantics. Every sentence adds information and there is no filler.

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

Completeness4/5

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

For a four-parameter, single-required-field send tool with no output schema, this covers what an agent needs: recipient scope, one-way semantics, and that the call is terminal rather than awaiting a reply. The remaining gap is error/failure signaling on unverified recipients, which matters for a notification tool.

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 description coverage is 100%, so every parameter already carries its own meaning, including the idempotency intent of external_id. The description adds no syntax, format, or precedence guidance beyond the schema, so the 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?

States a specific verb and resource ('Send a one-way notification ... on WhatsApp') plus concrete example payloads (build failed, order shipped, job finished). The 'one-way ... does not wait for a reply' phrasing behaviorally separates it from a question/answer sibling like ask_person, so an agent can pick correctly without opening schemas.

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?

Gives clear when-to-use context through the example triggers and states a when-not constraint ('never your customers'). It stops short of naming an alternative tool for the two-way case, leaving the agent to infer that ask_person fills that role.

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