Skip to main content
Glama

send_message

Send OneBot messages to QQ friends or groups via CQ-code strings or segment arrays, enabling text, media, and interactive content delivery in one call.

Instructions

Send any OneBot message to a friend or group: a CQ-code string or an array of segments, e.g. [{"type":"text","data":{"text":"hi"}},{"type":"image","data":{"file":"https://…"}}]. Segment types: text, at, face, mface, image, record, video, file, reply, forward, json, xml, poke, dice, rps, music, contact, markdown, location, share.

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": {
      "target": "<target>",
      "message": "<message>"
    },
    "name": "send_message"
  }
}

Input Schema

NameRequiredDescriptionDefault
targetYesWho to talk to: "qq:<QQ号>" for a friend/private chat, "group:<群号>" for a group, a bare number, or a friend remark/nickname/group name (must be unambiguous).
messageYesSegment array or CQ-code string

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

The annotations already declare that this is not read-only and is open-world but not destructive. The description adds useful payload-format context through the example array and the list of segment types, but it does not discuss side effects, permissions, rate limits, or failure behavior beyond what the annotations provide.

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 front-loaded with the core action and then supplies format details and the segment-type list. The long enumeration is useful rather than redundant, though it is dense and could be structured more readably.

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 two-parameter tool with fully described schema fields and safety annotations, the description provides enough detail to invoke the tool with a valid target and message payload. Its main completeness gap is the lack of explicit routing guidance among the many specialized send_* siblings.

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 adds value beyond the schema by giving a concrete segment-array example and enumerating supported segment types, which helps an agent construct valid message payloads.

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?

The description states a specific verb and resource: send an OneBot message to a friend or group. It makes clear this is a general-purpose sender and lists supported segment types, but it does not explicitly distinguish itself from specialized sibling tools such as send_text or send_image.

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 phrase 'Send any OneBot message' implies this is the flexible/general send tool, but there is no explicit guidance about when to prefer it over the many specialized send_* siblings. It also does not name alternatives or exclusions.

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

Deploy Server

Other Tools