Skip to main content
Glama

send_fake_forward

Build and send a merged-forward chat card from custom message nodes to share a transcript-style summary with a QQ friend or group.

Instructions

Send a 合并转发 card built from custom nodes (each with a display name, QQ number and content), e.g. to share a summary as a chat transcript.

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>",
      "nodes": "<nodes>"
    },
    "name": "send_fake_forward"
  }
}

Input Schema

NameRequiredDescriptionDefault
nodesYesMessages in the bundle
sourceNoCard title
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).
summaryNoCard footer

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 this is a non-read-only, open-world, non-destructive send, so the safety profile is covered. The description adds that the card is assembled from custom nodes, but does not disclose anything about delivery scope, permissions, failure modes, or how the card renders for recipients.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence that names the resource first and puts the illustrative use case last. No redundant or filler wording.

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?

For a 4-parameter send tool with full schema coverage and annotations, the definition is adequate: an agent knows what it builds and roughly why. It is missing any note on when this differs materially from real forwarding or what happens if the target is ambiguous, which the schema hints at but the description never addresses.

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 100%, so the schema already documents target formats, node fields, source, and summary. The description only restates the node fields (display name, QQ number, content) at a high level, adding no format or constraint detail beyond the schema.

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?

States a specific verb (send) and resource (a merged-forward card built from custom nodes) and clarifies the payload is synthetic rather than a real forwarded message, which implicitly separates it from the forward_* siblings. It stops short of naming any sibling outright.

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?

The phrase 'e.g. to share a summary as a chat transcript' gives one concrete use case, so the intended scenario is inferable. There is no explicit when-not guidance and no naming of alternatives such as send_forward_msg for forwarding genuine messages.

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