Skip to main content
Glama

send

Posts a message to a specified channel, including the public lobby or DM/server channels, by supplying the channel ID and text.

Instructions

Sends a message to a channel. channelId='lobby' is public to everyone; DM and server channels use their own channelId.

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": {
      "channelId": "<channelId>",
      "text": "<text>"
    },
    "name": "send"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYesMessage text
channelIdYesTarget channel ID (e.g. lobby)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv3.0.1
    • removedInput schema / additionalProperties
      Removed value: -false
  2. First observedv2.1.1

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare non-read-only, non-idempotent, open-world, non-destructive behavior, so the safety profile is covered. The description adds the channel-visibility distinction, but says nothing about who the message is sent as (relevant given use_account exists), duplicate risk from non-idempotency, or what happens with an invalid channelId. Useful but partial beyond the annotations.

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 short sentences, scope first and the channelId clarification second, with no filler or repetition of schema details.

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 two-parameter send with annotations covering side effects and no output schema, this is nearly sufficient. The remaining gap is how an agent obtains a DM or server channelId, but that reasonably lives with sibling tools.

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?

Schema coverage is 100%, so the baseline is 3; the description earns a bump by explaining that 'lobby' is the public channel and that DM and server channels use distinct IDs, which defines the identifier space the schema only names. It still says nothing about text formatting or length limits beyond the schema's maxLength.

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?

"Sends a message to a channel" gives a specific verb plus resource, and the second sentence clarifies the channelId naming space. It is not explicitly contrasted with siblings like read or open_dm, but the purpose is unambiguous without opening the schema.

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

Usage Guidelines3/5

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

The description hints at usage by explaining what 'lobby' means and that DM/server channels have their own IDs, which is implicit guidance on which channelId to supply. It never says when to prefer this over alternatives (e.g., calling open_dm first to obtain a DM channelId) and gives no exclusions or prerequisites.

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