Skip to main content
Glama

download_file_image_stream

Streams image downloads from a cached image ID, URL, or stream-directory file, returning file info, data chunks, and completion frames for incremental processing.

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_image_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.8/5.0
Behavior4/5

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

Annotations(readOnlyHint=false、openWorldHint=true、destructiveHint=false)已经给出安全和开放世界画像;description 补充了有价值的上下文,包括 `file_id` 的来源、可被接受的输入来源,以及流式帧顺序 `file_info → file_chunk* → file_complete`。它仍未说明每个分块携带什么、内存如何被消耗,或者部分流如何被清理,而这些对 agent 处理至关重要,因此这不是满分。

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?

篇幅短、前置信息清楚,并在开头给出来源约束和返回协议,而不是埋在后文。不过,括号里的来源列表和 `invoke_action` 提及被压缩成密集的简写,需要仔细阅读。

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?

没有 output schema,因此 description 正确地承担起解释返回帧协议的责任。对于一个有 annotations 的 3 参数工具来说,整体足够;唯一真正的缺口是流式使用约定(超时、重试,或者必须全部消费)没有被覆盖。

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

Parameters4/5

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

Schema 描述覆盖率为 100%,且已经记录了 `file`、`file_id` 和 `chunk_size`,因此基线是 3。description 在 schema 之外增加了语义:它说明 `file_id` 来自当前账号的图片消息,并确认 `file` 覆盖缓存 id、URL 和流临时目录路径。

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?

开头明确写出动词和资源(“以流式方式下载图片”),并列出被接受的三种来源(缓存图片 id、URL、stream 临时目录本地文件)。它没有点名 `download_file_stream` / `download_file`,因此 agent 必须从“图片”与通用的流式兄弟工具 `download_file_stream` 推断区别。

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?

它说明 `file_id` 来自当前账号的图片消息,且该工具通过 `invoke_action` 调用,这有用但不完整的前置条件。它没有说明何时使用它,而不是 `download_file_stream`、`download_file`、`get_image` 或 `view_image`,也没有说明这些替代项是否仍然适用。

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