Skip to main content
Glama

download_file_record_stream

Streams voice and file records from your QQ account by cached file ID, URL, or stream temp path, returning file info, chunks, and completion frames.

Instructions

以流式方式下载语音(缓存语音 id / URL / stream 目录本地文件) file_id 来自当前账号语音消息;经 invoke_action 调用。 Returns: 流式帧:file_info → file_chunk* → file_complete

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": "download_file_record_stream"
  }
}

Input Schema

NameRequiredDescriptionDefault
fileNo文件路径(限 stream 临时目录)/ http(s) URL
file_idNo文件 ID(缓存的图片/语音 id)
chunk_sizeNo分块大小(字节,默认 64KB)

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 openWorldHint=true, destructiveHint=false, and readOnlyHint=false. The description adds the streaming return frame protocol (file_info → file_chunk* → file_complete), which is useful. It does not explain side effects implied by readOnlyHint=false, such as temp file creation or cleanup, or auth requirements.

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 input and return behavior. The parenthetical input list and frame sequence are dense but directly useful, with no filler.

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?

No output schema exists, and the description compensates by describing the streaming frame sequence. Combined with annotations and full parameter descriptions, it is nearly complete, though side-effect and temp-file behavior remains unaddressed.

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 100%, so all three parameters are already documented. The description adds file_id provenance (current account voice message) and source variants, but does not clarify chunk_size behavior or how file and file_id are prioritized when multiple inputs are supplied.

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 the specific operation (streaming download) and resource (voice), and lists accepted source types: cached voice id, URL, or local file in the stream temp directory. It does not explicitly contrast with sibling tools such as download_file_image_stream or download_file_stream, so sibling differentiation is only implicit.

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 the key precondition that file_id comes from a voice message in the current account and notes the tool is called via invoke_action. It does not state when to prefer it over download_file_stream or download_file_image_stream, nor does it state 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