Skip to main content
Glama

send_text

Send text messages to QQ friends or groups, with optional @mentions, quote replies, emojis, images, and inline formatting tokens for targeted communication.

Instructions

Send a text message to a friend or group. Inline tokens: [@QQ号] mention, [@all] @全体, [face:ID] QQ emoji, [reply:message_id] quote, [image:URL或路径] picture. Or use reply_to / mention.

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>",
      "text": "<text>"
    },
    "name": "send_text"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYesMessage text
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).
mentionNoQQ numbers to @ at the start ("all" for 全体成员)
reply_toNomessage_id to quote-reply

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare a non-readonly, open-world, non-destructive send operation, so the safety profile is covered. The description adds genuinely useful behavioral context — that inline markup tokens are parsed inside the message body and that mention/reply can alternatively be supplied as structured parameters. It says nothing about rate limits, permission requirements for groups, or failure behavior when a target is ambiguous.

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?

Two sentences, front-loaded with the purpose and then a dense but scannable token reference; no filler. The trailing 'Or use reply_to / mention' is slightly terse and could be clearer about how inline tokens interact with the structured parameters, but nothing is wasted.

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

Completeness3/5

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

For a 4-parameter tool with full schema coverage but no output schema, the description covers message composition well. It leaves gaps on what is returned (presumably a message_id, which reply_to depends on) and on which of the many sibling send tools this one replaces, both material for correct invocation.

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%, establishing a baseline of 3, but the description earns extra credit by documenting the inline token grammar ([@QQ号], [@all], [face:ID], [reply:message_id], [image:URL或路径]) that the schema's 'Message text' description omits entirely. That is real semantic content an agent could not infer from the schema alone.

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 ('Send a text message to a friend or group'), which distinguishes it from the many media-sending siblings like send_image or send_voice. However, it does not distinguish itself from send_message, send_msg, send_group_msg, or send_private_msg, which by name appear to overlap heavily.

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

Usage Guidelines2/5

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

There is no guidance on when to use this tool versus the numerous alternative send_* tools, despite the sibling list containing obvious-looking overlaps (send_message, send_msg, send_group_msg, send_private_msg). The clause 'Or use reply_to / mention' concerns parameter choice within this tool, not tool selection, so the agent gets no routing help.

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