Skip to main content
Glama

Send a message

send_message

Transmit text messages to contacts or channels on a MeshCore network, with optional delivery acknowledgement for direct messages.

Instructions

Transmit a text message. target is a contact (name or hex public-key prefix) or a channel (#name, #index, or a bare channel index). A resend is a second transmission — not idempotent. Set confirm: true to wait for the delivery ack and report whether it arrived + the round-trip time. Confirmation applies to direct (contact) messages only: a channel/broadcast has no single recipient to ack, so a confirm: true channel send returns confirmationNotApplicable: true (and no delivered) rather than silently ignoring the request.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
targetYesa contact (name or hex public-key prefix) or a channel (`#name`, `#index`, or a bare channel index)
textYesthe message text to transmit
confirmNowait for and report the delivery ack + round-trip. Direct (contact) messages only — for a channel/broadcast send the result reports `confirmationNotApplicable: true` instead (no single recipient to ack)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
kindYes
contactNo
publicKeyNo
channelIdxNo
channelNameNo
textYes
routeNohow a contact send was routed
deliveredNodelivery ack result (only when confirm requested, contact sends): true if acked, false if none arrived in the window
roundTripMsNoround-trip time of the delivery ack, ms (when delivered)
confirmationNotApplicableNotrue when confirm was requested for a channel/broadcast send: there is no single recipient to ack, so delivery confirmation does not apply (delivered/roundTripMs are correctly absent) — distinct from a fire-and-forget send
Behavior5/5

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

The description adds non-idempotent behavior and confirmation scope beyond annotations (readOnlyHint=false, idempotentHint=false), with no contradictions.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is concise and front-loaded with purpose, but the sentences are somewhat dense; slightly better structure would merit a 5.

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

Completeness5/5

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

Given the presence of an output schema, the description adequately covers input semantics, idempotency, and confirmation details without needing to explain return values.

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 100%, and the description largely echoes schema descriptions without adding new semantic value beyond the structured data.

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 'Transmit a text message' and specifies target formats (contact or channel), making the tool's purpose distinct from siblings like broadcast_advert.

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 explains how to use the tool, including confirm behavior and channel limitations, but does not explicitly state when to avoid using it or compare with alternatives.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/dpup/meshcore-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server