@runehand/mcp-server

Send message

send_message

Send a message in an existing conversation to reach customers on external channels like WhatsApp or Telegram when the chat isn't on the web.

Instructions

Send a message as the agent in an existing conversation. Delivers to the external channel (WhatsApp, Telegram, etc.) when the conversation is not on the web channel.

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": {
      "conversation_id": "<conversation_id>",
      "content": "<content>"
    },
    "name": "send_message"
  }
}

Input Schema

Name	Required	Description	Default
`content`	Yes	Message text, max 4096 characters.
`conversation_id`	Yes	UUID of the conversation to send the message in.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 20, 2026

TDQS

A4/5.0

Behavior3/5

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

With no annotations, the description carries the full burden. It discloses the core behavior and the channel-specific delivery nuance, which adds value. However, it does not mention potential side effects, required permissions, or failure scenarios. For a write operation, more behavioral context could be expected.

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 two sentences, front-loaded with the main action, and includes only essential additional context about channel delivery. Every word earns its place, making it highly concise and well-structured.

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 simple tool with two parameters and no output schema, the description adequately covers the main purpose and the only exception (web vs. external channel). It does not over-explain trivial details, and the lack of an output schema means return values are not required to be described. Slightly more detail on delivery status would improve completeness, but it is generally sufficient.

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%, with both content and conversation_id having descriptive text in the schema. The tool description adds no additional parameter details beyond what the schema already provides, so it meets the baseline but does not enhance understanding.

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 clearly states the action: 'Send a message as the agent in an existing conversation.' This is a specific verb+resource combination, and the channel delivery nuance further clarifies its scope. It is distinct from sibling tools like list_conversations or create_lead, which are not messaging tools.

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?

The description implies the tool is used for sending messages in existing conversations, and the external channel condition provides context on when delivery differs. It does not explicitly state when not to use it or mention alternatives, but since no sibling tool overlaps in function, this is adequate.

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

Deploy Server