Skip to main content
Glama

send_voice

Sends a voice message to a QQ friend, group, or contact using an audio URL, file path, or base64; audio is converted automatically before delivery.

Instructions

Send a voice message (mp3/wav/silk/amr… from URL, path or base64; converted automatically).

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

Input Schema

NameRequiredDescriptionDefault
fileYesURL / path / base64 of the audio
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).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior4/5

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

The annotations already disclose openWorldHint=true and destructiveHint=false. However, the description adds genuinely new behavioral information: that the input becomes audio automatically, which formats are accepted (mp3/wav/silk/amr), and which input sources are valid (URL, path, or base64). It still does not cover size limits, rate limits, or what happens when a send fails, but the conversion detail is real added value.

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?

The definition is one front-loaded sentence, with the resource and supported formats carried in a compact parenthetical. That structure is efficient. However, a little more guidance or a cross-reference would make the description fully useful.

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

Completeness4/5

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

This is a simple two-parameter tool with annotations covering safety and no output schema, so the bar for the description is modest. Format handling and accepted sources are covered, but the description is silent on what happens after a successful or failed send, which would matter for a message-sending operation. It is still largely 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 description coverage is 100% and both parameters are described in the schema: one is the audio source, and the other is the target format. The description restates the accepted source types (URL, path, or base64) without adding syntax, prioritization, or constraints beyond what the schema already gives. It therefore matches the baseline for a fully documented two-parameter tool.

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 gives a specific verb and resource: "Send a voice message". It is clearly distinct from siblings like send_image, send_video, or send_text because their resource type is different. The description adds no explicit sibling comparison, but the resource type alone makes the purpose unambiguous.

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?

The description only implies when to use the tool: for audio or voice content, automatically converting formats. It never says when not to use it, names no alternative tool, and does not mention any prerequisites or grouping of related tools. This is adequate but has clear gaps in guidance.

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