Skip to main content
Glama

get_ai_characters

Read-only

Fetch categorized AI voice characters by QQ group ID, returning role names, IDs, and preview URLs so users can choose a voice for group interactions.

Instructions

获取 AI 语音角色 将 group_id 替换为当前账号可访问的群号。 Returns: 按分类分组的 AI 语音角色列表,每组含分类名与角色(id、名称、试听 URL)。

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

Input Schema

NameRequiredDescriptionDefault
group_idYes群号
chat_typeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered. The description adds real behavioral value beyond them by spelling out the response structure (grouped by category, each entry with id, name, and preview URL) and the constraint that group_id must be an account-accessible group — an authorization caveat not present in the annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two compact sentences: purpose first, then return value. Every clause carries information, and no filler or repetition is present.

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?

Because there is no output schema, the description correctly assumes responsibility for describing the return value, which it does adequately. However, with an unexplained second parameter (chat_type) and no positioning against sibling retrieval tools, an agent still lacks enough to call this confidently in ambiguous cases.

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 50% schema coverage, the description must compensate for the gaps. It does add an access constraint for group_id beyond the schema's bare '群号', but chat_type is undocumented in both the schema and the description, leaving half the parameters 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?

States a specific verb and resource ('获取 AI 语音角色') and even summarizes the return shape (category-grouped list of characters). It never distinguishes itself from nearby siblings such as get_ai_record or send_group_ai_record, so an agent must infer the difference from names alone.

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?

The only guidance is a parameter hint: substitute group_id with a group number the current account can access. There is no statement of when to use this instead of the other AI-record tools, no prerequisites, and no 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