Skip to main content
Glama

get_ai_record

Generates an AI voice record for a QQ group from a character ID and text, ready to send as a voice message.

Instructions

生成 AI 语音 character 原样使用 get_ai_characters 的 character_id;send_group_ai_record 会直接发送语音。

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": "get_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 readOnlyHint=false, destructiveHint=false, openWorldHint=true, so the schema already flags this as a non-destructive generative write. The description adds real value beyond that: it clarifies that generation does NOT transmit the voice, with transmission delegated to send_group_ai_record. It says nothing about rate limits, quota, auth needs, or whether generated audio persists.

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 compact clauses with zero filler, and the core purpose (generate AI voice) is front-loaded ahead of the cross-references. Dense but readable; it earns almost every word it uses.

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 generative tool with no output schema and only 25% schema coverage, the definition leaves the caller guessing what comes back (a record ID? a file path?) and what 'text' and 'chat_type' should contain. The minimal viable picture is there, but the low-coverage parameters and absent return contract are real gaps.

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% — only group_id ('群号') is documented. The description compensates for exactly one gap by specifying that character must be a character_id sourced from get_ai_characters, which is meaningful. The required 'text' and the 'chat_type' parameter remain completely unexplained in both schema and description.

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 opens with a concrete verb+resource ('生成 AI 语音') that resolves the ambiguity of the vague name 'get_ai_record', and it explicitly distinguishes this tool from send_group_ai_record (which sends instead of only generating). It stops short of 5 because it never says what the generated artifact actually is (a record ID, file, message) or how the caller obtains it.

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 actionable routing guidance: use character_id from get_ai_characters verbatim, and note that send_group_ai_record delivers the voice directly, implying this tool only generates. No explicit when-not conditions or prerequisites (permissions, group membership) are stated, so it falls short of a full 5.

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