Skip to main content
Glama

get_file

Read-only

Fetches cached QQ image or voice file information, attempting image first then voice; use the group file URL tool for group files.

Instructions

获取文件信息(仅图片/语音缓存;群文件请用 get_group_file_url) 仅查询已缓存的图片或语音,先尝试图片,再尝试语音。

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_file"
  }
}

Input Schema

NameRequiredDescriptionDefault
fileNo
file_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds real behavior beyond that: it only resolves cached items and applies a two-step image-then-voice fallback. It does not disclose what happens when neither lookup succeeds, which keeps it from a 5.

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?

Two compact sentences with zero filler and the scope restriction front-loaded before the sibling reference. The dense parenthetical and slash notation (图片/语音缓存) make it slightly cryptic, but nothing is wasted.

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?

Scope, alternatives and fallback order are covered, and the read-only profile is supplied by annotations with no output schema to explain. However, for a tool whose two optional parameters are entirely undocumented, the definition leaves the agent guessing how to actually supply the file, so it is adequate rather than complete.

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% for the two parameters (file, file_id), so the description must carry the burden. It never explains what file versus file_id represent, which one takes precedence, or what format either expects; the image-then-voice note concerns resolution order, not parameter meaning.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource (获取文件信息 / get file info) and immediately narrows the resource to cached image/voice files, explicitly naming the sibling get_group_file_url as the path for group files. An agent can distinguish get_file from the group-file and download tools without inspecting any schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives explicit when-to-use (only already-cached images or voice), when-not (group files, routed to get_group_file_url), and even an internal resolution order: try image first, then voice. That is a complete routing rule, not an implied one.

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