Skip to main content
Glama
1msg MCP

1msg MCP

Official
by 1msg

get_whatsapp_business_encryption

Retrieve the WhatsApp business public key and signature status for a phone number before publishing or sending Flows that use data encryption.

Instructions

Retrieve the WhatsApp business public key and signature status for this channel's phone number. Required before publishing or sending Flows that use data encryption.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_whatsapp_business_encryption"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.0

TDQS

A3.8/5.0
Behavior3/5

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

No annotations exist, so the description carries the full burden. 'Retrieve' implies a non-mutating read, and the description names the two artifacts returned (public key, signature status), which is useful. It does not disclose permission/auth requirements, behavior when encryption is unconfigured, or whether the key can rotate between calls.

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?

Two sentences, both load-bearing: the first states exactly what is returned, the second the prerequisite that motivates calling it. The key information is front-loaded and nothing is padded.

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

Completeness3/5

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

For a zero-parameter read with no output schema, the description does reasonably well by naming the two returned fields and the reason to call it. However, with no output schema the agent still has no notion of response shape, field formats, or error behavior when encryption is not yet configured, which leaves a meaningful gap.

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?

The tool takes zero parameters, so there is no parameter semantics to clarify; the baseline for a parameterless tool applies. The description correctly adds the implicit scoping ('this channel's phone number') that explains why no arguments are needed.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb-plus-resource pairing ('Retrieve the WhatsApp business public key and signature status') scoped to this channel's phone number, which an agent can distinguish from the write-side sibling by name alone. It stops short of explicitly naming set_whatsapp_business_encryption as the counterpart, so differentiation is inferred rather than stated.

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 clear precondition: call this before publishing or sending Flows that use data encryption. That tells the agent when to use it. There is no guidance on when it is unnecessary or what to do if it fails, and no sibling alternative is named.

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