YCloud WhatsApp API MCP Server

wa_msg_send_directly

Send WhatsApp messages through the YCloud API. Use this tool to communicate directly with contacts by composing and delivering text messages via the WhatsApp platform.

Instructions

Send a message directly

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

Input Schema

Name	Required	Description	Default
`body`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedAug 15, 2025

TDQS

D1.7/5.0

Behavior1/5

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

With no annotations provided, the description carries the full burden but offers no behavioral details. It does not disclose permissions needed, rate limits, side effects, or response format, which is critical for a messaging tool.

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?

The description is extremely concise with a single sentence, 'Send a message directly', which is front-loaded and wastes no words, though this brevity contributes to its inadequacy in other dimensions.

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

Completeness1/5

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

For a messaging tool with no annotations, no output schema, and an undocumented parameter, the description is completely inadequate. It lacks essential context like target recipient, message type, or error handling, making it insufficient for effective use.

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

Parameters1/5

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

The input schema has 1 parameter with 0% description coverage, and the description adds no information about the 'body' parameter's meaning, format, or constraints, failing to compensate for the schema's lack of detail.

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

Purpose2/5

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

The description 'Send a message directly' restates the tool name 'wa_msg_send_directly' with minimal elaboration, making it tautological. It specifies the verb 'send' and resource 'message' but lacks detail about what distinguishes it from sibling tools like 'wa_msg_send' or the context of 'directly'.

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

Usage Guidelines1/5

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

No guidance is provided on when to use this tool versus alternatives, such as 'wa_msg_send'. The description does not mention prerequisites, exclusions, or specific scenarios, leaving usage unclear.

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