Skip to main content
Glama

upload_group_file

Uploads a file to a QQ group using the group ID and a server-readable file path, with optional display name, folder, and folder ID.

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": {
      "group_id": "<group_id>",
      "file": "<file>"
    },
    "name": "upload_group_file"
  }
}

Input Schema

NameRequiredDescriptionDefault
fileYes
nameNo
folderNo
group_idYes群号
folder_idNo
upload_fileNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false and openWorldHint=true, so the write semantics are covered. The description adds two things beyond that: the file argument must be a path on the server side ('SnowLuma 服务端'), not a client path, and the return shape is { file_id }. It says nothing about permission requirements, size limits, or overwrite behavior, which matters for an open-world upload.

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, action first, followed by the critical path caveat and the return value. No filler; the only cost is that the mixed-language phrasing reads slightly abruptly, but nothing is redundant.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 6-parameter mutation with 17% schema coverage and no output schema, the definition is thin: it covers the required file path and the return value but leaves four optional parameters, their defaults, and any permission or size preconditions undocumented. An agent could call it, but only by guessing at folder/name/upload_file behavior.

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 only 17% — just group_id carries '群号' — so the description is obligated to compensate for the other five parameters. It clarifies only `file` (server-side path, not a local path) and, indirectly, the response. `name`, `folder`, `folder_id` and `upload_file` (including its default true and what false means) remain completely unexplained in both schema and description.

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 opens with a specific verb+resource, '上传群文件' (upload group file), which contrasts naturally with the sibling upload_private_file. It does not explicitly name alternatives, but the group scope is unambiguous.

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?

There is no when-to-use guidance and no mention of the obvious alternatives (upload_file_stream, upload_private_file, upload_forward_msg) or when each is appropriate. The agent must infer the choice purely from tool names.

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