Skip to main content
Glama

upload_forward_msg

Uploads merged forward message resources without sending a chat message, returning a res_id for later use.

Instructions

上传转发消息 仅上传合并转发资源,不发送聊天消息;message_id=0 是占位值,后续使用 res_id。

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": "upload_forward_msg"
  }
}

Input Schema

NameRequiredDescriptionDefault
messageNo转发节点数组;节点 content 内的 reply.data.message 可提供自定义引用内容(字符串或消息段),qq/time/seq 可选;仅用于转发内引用预览。
group_idNo
messagesNo转发节点数组;节点 content 内的 reply.data.message 可提供自定义引用内容(字符串或消息段),qq/time/seq 可选;仅用于转发内引用预览。

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/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-but-not-destructive profile is covered. The description contributes useful behavior context by disclaiming message sending and explaining that message_id=0 is a placeholder superseded by res_id, though the gap between annotations and description isn't a contradiction.

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 tight clauses, front-loaded with the core action before the clarifying negation. No filler; only the trailing res_id note is slightly terse for an agent unfamiliar with the platform.

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?

This is an ambiguous platform-specific resource-upload tool with no output schema, yet the description omits key context: what happens to the returned resource, how group_id scopes the upload, and why both message and messages exist. It covers the 'doesn't send' semantics well but leaves the caller guessing on parameters.

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 67%, and the description clarifies the returned message_id=0 placeholder and the res_id handoff, which the schema does not state. However it adds nothing about group_id (undocumented in the schema) and does not disambiguate the near-duplicate message and messages parameters, whose descriptions are identical.

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?

States a specific verb+resource (上传转发消息) and immediately scopes it: '仅上传合并转发资源,不发送聊天消息', which cleanly separates it from the send_forward_msg / send_group_forward_msg family of siblings without needing to open 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 Guidelines4/5

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

Makes the usage context clear through negation (upload only, no chat message sent) and hints at the follow-up step ('后续使用 res_id'), which tells the agent this is a preparatory call. It stops short of naming which sibling to call next to actually send the merged forward.

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