Skip to main content
Glama

send_group_ai_record

Sends AI-generated voice messages to a QQ group using a character ID and input text, returning the OneBot message ID for tracking.

Instructions

发送 AI 语音到群 character 原样使用 get_ai_characters 的 character_id;send_group_ai_record 会直接发送语音。 Returns: { message_id }:已发送 AI 语音的 OneBot 消息 ID。

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": {
      "group_id": "<group_id>",
      "character": "<character>",
      "text": "<text>"
    },
    "name": "send_group_ai_record"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYes
group_idYes群号
characterYes
chat_typeNo

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?

Annotations already declare this as a non-read-only, non-destructive, open-world send, so the safety profile is covered. The description adds that it 'directly sends voice' (no confirmation step) and discloses the return shape { message_id }, which is genuinely useful, but says nothing about failure modes, permissions, or whether the message is revocable.

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?

Purpose and the return value are front-loaded in a short, dense pair of sentences with no filler. The clause 'send_group_ai_record 会直接发送语音' partly restates the tool name and is the only mild redundancy.

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 send tool with no output schema, the description supplies the return shape and the character sourcing rule, which covers the two riskiest unknowns. However, chat_type is left unexplained and there is no note on what happens if the send fails, leaving the definition adequate but not complete.

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?

Schema coverage is only 25% – group_id is documented as 群号, but text, chat_type, and the format of character are undocumented in the schema. The description compensates for character by specifying it must be an exact character_id from get_ai_characters, but text and chat_type (default 1) remain semantically opaque.

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 names a specific verb and resource ('发送 AI 语音到群') and pins the key input to its source, telling the agent to reuse the character_id from get_ai_characters verbatim. That distinguishes it from the character-listing sibling, but it does not contrast with the nearby send_voice / send_group_msg tools that also push audio.

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?

It gives a concrete prerequisite workflow: fetch a character first via get_ai_characters and pass its character_id unchanged. It stops short of stating when to prefer this over send_voice or send_group_msg, so it is clear context rather than a full decision rule.

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