Skip to main content
Glama

send_file

Sends or uploads a file to a QQ friend or group from a URL, server path, or base64 data, with optional file name and group folder.

Instructions

Send a file to a friend or upload it to a group (群文件). Source: URL, path on the server, or base64.

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": {
      "target": "<target>",
      "file": "<file>"
    },
    "name": "send_file"
  }
}

Input Schema

NameRequiredDescriptionDefault
fileYesURL / path / base64
nameNoFile name shown in QQ (default: from path/URL)
targetYesWho to talk to: "qq:<QQ号>" for a friend/private chat, "group:<群号>" for a group, a bare number, or a friend remark/nickname/group name (must be unambiguous).
folder_idNoGroup file folder id (groups only)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/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 safety profile is carried structurally. The description adds a meaningful behavioral cue by framing the group case as uploading into 群文件 (group file storage) rather than sending a chat message, but it says nothing about size limits, permission requirements, overwrite behavior, or whether a message is also emitted.

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 short clauses with the purpose front-loaded and the source types as a compact trailing fragment. The source enumeration is mild redundancy against the schema, but nothing is padded or buried.

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?

With four fully documented parameters, no output schema, and annotations covering safety, the description supplies what an agent needs to route the call correctly. Gaps are behavioral rather than structural: no guidance on ambiguous nicknames, failure modes, or whether folder_id applies outside group targets beyond the parenthetical hint.

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% and each parameter carries its own description, including the 'qq:<QQ号>' / 'group:<群号>' addressing syntax and the folder_id group-only constraint. The description's 'URL / path / base64' phrase merely restates the file parameter and adds no new meaning, so the baseline of 3 applies.

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 definition uses a concrete verb plus resource ('Send a file'), splitting the two real use cases (friend chat vs group 群文件), so an agent knows this is the outbound-file tool. It stops short of naming near-neighbors such as upload_group_file or upload_private_file, so the differentiation from those siblings is left to inference.

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?

Usage is only implied: the description pairs 'friend' and 'group' targets with the two purposes, and the schema's target field spells out the addressing forms. There is no explicit statement of when to prefer this tool over upload_group_file / upload_private_file / upload_file_stream, nor any prerequisite or exclusion.

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