Skip to main content
Glama

upload_private_file

Upload a local file from the server and send it to a specified QQ friend, returning a file ID for later reference.

Instructions

上传私聊文件 示例路径位于 SnowLuma 服务端,须替换为该服务可读取的实际文件。 默认上传并发送给该好友。 Returns: { file_id: string }

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": {
      "user_id": "<user_id>",
      "file": "<file>"
    },
    "name": "upload_private_file"
  }
}

Input Schema

NameRequiredDescriptionDefault
fileYes
nameNo
user_idYes
upload_fileNo

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?

Annotations already declare a non-read-only, non-destructive, open-world operation. The description usefully adds that 'file' is a server-side path readable by the SnowLuma service and must be replaced with a real one, plus that uploading sends to the friend by default and returns file_id. It stops short of covering failure modes, size limits, or permission requirements for the outbound send.

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?

Three short sentences front-load the purpose, then the path caveat, then the default behavior and return shape. No filler, though the mixed-language packaging and the trailing 'Returns' line are slightly clipped rather than elegant.

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?

Given no output schema, including the return shape ({ file_id: string }) is the right call, and the server-path warning is exactly the kind of detail that prevents a failed call. Gaps remain around the undocumented name/user_id parameters and the consequences of the outbound send, but the essentials are present.

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 0% for four parameters, so the description must compensate and only partly does: it clarifies 'file' as a server-side path and 'upload_file' as defaulting to true with immediate send. It says nothing about 'user_id' or 'name', leaving half the surface undocumented in both schema and prose.

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 opening phrase '上传私聊文件' gives a specific verb plus resource and implicitly separates it from the group-upload siblings by naming the private-chat scope. It is clear what the tool does, but no sibling (e.g. upload_group_file, upload_file_stream) is named to sharpen the boundary.

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

Usage Guidelines2/5

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

The description only states the default behavior ('默认上传并发送给该好友'), which implies sends happen immediately, but it never says when to prefer this tool over upload_file_stream or send_file, nor any precondition or exclusion. An agent must infer selection from the name alone.

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