Skip to main content
Glama
Sign In

Widely

by com.widely-mobile
OverviewDiscussionsAdmin

Send a WhatsApp code

whatsapp_number_request_code

Asks WhatsApp to text or call a number this account owns with a registration code. method is sms or voice. forward_to is optional and only for a voice call: a phone already verified on this account. When the person reads the digits, pass them to whatsapp_number_verify_code.

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": {
      "did_id": "<did_id>"
    },
    "name": "whatsapp_number_request_code"
  }
}

Input Schema

NameRequiredDescriptionDefault
did_idYes
methodNosms texts the code. voice calls with the code.
forward_toNoA verified phone on this account. Used only when method is voice.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare non-read-only, non-idempotent, non-destructive, open-world behavior, and the description adds context beyond them: the number must belong to this account, and forward_to is valid only for voice and only for an already-verified phone. It does not mention that repeated calls send additional codes or any rate limiting, which matters for a non-idempotent send.

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 short sentences, front-loaded with the action, then parameter constraints, then the handoff to the verify tool. No filler and nothing repeated for its own sake.

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?

With no output schema, the description could have said what a successful request returns or what a failure looks like, and it omits that. Otherwise it is complete for a simple three-parameter send operation whose safety profile is already carried by annotations.

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 67%, with method and forward_to already described in the schema; the description largely restates them while adding the useful constraint that forward_to requires a verified phone and voice method. The required did_id parameter carries no schema description, and the description only implies it via 'a number this account owns', so that gap is not fully compensated.

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 specific verb and resource: it asks WhatsApp to send a registration code to a number the account owns, by SMS or voice. It is also explicitly distinguished from the sibling it pairs with, whatsapp_number_verify_code, so an agent can separate the two without opening either schema.

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 states the triggering situation (requesting a code) and names the exact follow-up tool once the digits are read, which is real routing guidance. It stops short of saying when not to use it, for example what happens if a code was already requested or whether a new request invalidates the old one.

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

All Widely toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources