Skip to main content
Glama

get_record

Read-only

Retrieves QQ voice message details and download URL, and when out_format is set, converts the audio and returns it as base64 for message workflows.

Instructions

获取语音信息;传 out_format 则服务端转码并附带 base64 file 来自语音消息段;格式转换依赖服务端可用的转换工具,成功时增加 out_format 和 base64。 Returns: 语音信息(file/url 为向 QQ 获取的当前下载地址);资源元数据缺失或远端获取失败时返回错误。out_format 指定时附带转码后的 base64。

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_record"
  }
}

Input Schema

NameRequiredDescriptionDefault
fileNo
file_idNo
out_formatNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

Beyond the readOnly/openWorld/non-destructive annotations, the description discloses useful behavior: transcoding depends on server-side conversion tools being available, success adds out_format and base64 fields, and missing resource metadata or remote fetch failure produces an error. That is real added context; however, it never states the fallback when transcoding tools are unavailable, whether the base64 is omitted or an error is raised, so the behavioral picture is incomplete.

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 description front-loads the core conditional (pass out_format, get transcoded base64) before the Returns block. It is somewhat repetitive: the out_format/base64 relationship is restated in the trailing sentence, so trimming that clause would sharpen it.

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 read-only tool with three optional parameters and no output schema, the definition does reasonably well: it documents return fields, the QQ download address, and error conditions. It falls short on the undocumented file_id parameter and the rate/availability caveat around transcoding, both of which an agent would need before calling reliably.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must carry the parameter burden, and it only partly does. It explains out_format (transcoding plus base64 attachment) and partially explains the file parameter (current download address from QQ), but it says nothing about file_id or how file and file_id relate or which to prefer, so at least one of three parameters is left undefined.

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: 获取语音信息 (retrieve voice/audio message info), and clarifies that the record is drawn from 语音消息段 (voice message segments) and that file/url is a current download address fetched from QQ. That is enough for an agent to know this is a voice-record reader, not a generic file getter; no sibling such as get_file or download_file_record_stream is named, so the tool is identified by its own terms rather than by contrast.

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 clear conditional: passing out_format triggers server-side transcoding with an attached base64 payload. It offers no guidance on when to choose this tool over the many other get_* sibling tools, nor what to do when transcoding is unavailable beyond noting the dependency; the when-to-use intent is implied rather than stated.

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