Skip to main content
Glama

send_private_msg

Deliver a private QQ message to a specified user by QQ number; include a source group_id for temporary sessions. Returns the sent message ID.

Instructions

发送私聊消息 替换目标好友 QQ 号;临时会话需另传来源 group_id。 Returns: { message_id: number }

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": {
      "user_id": "<user_id>",
      "message": "<message>"
    },
    "name": "send_private_msg"
  }
}

Input Schema

NameRequiredDescriptionDefault
messageYesOneBot message: string | segment[] | object. In segment arrays, text segments whose text field is exactly "" are compatibility placeholders and do not count as sendable segments; missing, null, and whitespace-only text remain subject to normal validation.
user_idYes
group_idNo
auto_escapeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare this is a non-destructive write to an open world, so the safety profile is covered. The description adds the return shape ({ message_id }) and the temporary-session constraint, but says nothing about permissions, rate limits, or failure behavior for an outbound message send.

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 short clauses plus the return value, with the target-scoping rule front-loaded. Nothing is padded, though the phrasing of the user_id clause ("替换目标好友 QQ 号") is slightly awkward and could be read ambiguously.

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 four-parameter mutation tool with no output schema, the description usefully supplies the return value and the group_id dependency. It still leaves auto_escape and general send semantics unexplained, so an agent would need to open the schema to call this correctly.

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?

With only 25% schema description coverage, the description does real work by explaining that user_id is the target friend's QQ number and that group_id is the source group for temporary sessions. However, auto_escape is left completely undocumented in both schema and description, so compensation is incomplete.

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 a private message) and scopes it to a friend's QQ number, which cleanly separates it from the group-message siblings. It does not name any sibling explicitly, so the distinction with send_msg / send_private_forward_msg is only implicit.

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?

It gives one concrete usage rule — temporary sessions require an extra source group_id — which is genuinely actionable. It offers no guidance on when to prefer this over the generic send_msg or the private-forward variant, leaving the main routing decision to inference.

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