Skip to main content
Glama

send_message

Sends text, image, voice, video, or file messages to a specified platform target (user, group, channel, guild, or thread) via the configured adapter.

Instructions

向指定平台发送消息(经平台适配器 SendDSL)。

Args: platform: 平台名(如 onebot11,先用 list_adapters 确认) target_type: 目标类型:user(私聊)/ group(群聊)/ channel / guild / thread(private 也可,自动转为 user) target_id: 目标 ID(用户 ID / 群号,字符串,≤128 字符) method: 发送方法名:Text(文本)/ Image / Voice / Video / File(后四者为 URL 或 base64) content: 消息内容(Text 为文本字符串;媒体类为 URL 或 base64 字符串) account: 可选,指定发送账户 ID(多 bot 部署时区分用哪个账户发;缺省用适配器默认账户)

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": {
      "platform": "<platform>",
      "target_type": "<target_type>",
      "target_id": "<target_id>",
      "method": "<method>",
      "content": "<content>"
    },
    "name": "send_message"
  }
}

Input Schema

NameRequiredDescriptionDefault
methodYes
accountNo
contentYes
platformYes
target_idYes
target_typeYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full disclosure burden, and it does reveal useful traits: target_type aliasing ('private 也可,自动转为 user'), media accepted as URL or base64, and default-account fallback. It says nothing about permissions, rate limits, partial failures, or whether success means queued versus delivered — material gaps for a side-effecting send tool with zero annotation coverage.

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?

A single front-loaded purpose line followed by per-parameter notes; every line adds information and nothing is repeated from the schema titles.

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?

Six parameters with 5 required and no annotations is heavy reliance on prose, and the description covers each parameter plus the multi-account case. With an output schema present, return values needn't be explained, but missing error/failure semantics and permission requirements leave it slightly incomplete.

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 description coverage is 0%, so the description must carry parameter meaning, and it documents all six parameters including a length bound on target_id (≤128 字符), the acceptable values for target_type and method, and the semantics of content varying by method. It falls short of 5 only because platform names and method availability are given as examples rather than an authoritative list.

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?

States a specific verb and resource ('向指定平台发送消息') plus the mechanism used ('经平台适配器 SendDSL'), which goes slightly beyond restating the tool name. It doesn't explicitly contrast itself with read-oriented siblings like recent_messages, but the send-versus-read split is unambiguous from the wording.

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?

Gives a concrete prerequisite for the platform parameter ('先用 list_adapters 确认') and explains when to supply the optional account parameter ('多 bot 部署时区分用哪个账户发'). There is no explicit when-not-to-use guidance, which keeps it short of a 5.

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