Skip to main content
Glama

send_packet

Send a raw SSO packet using a verified command and matching hex payload for protocol-level QQ operations; replace example placeholders before sending.

Instructions

发送原始 SSO 包(cmd + hex data) 仅供有协议经验的调用方:cmd 和 data 必须成对替换为已验证的命令与十六进制请求;示例占位符不可直接发送。

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": {
      "cmd": "<cmd>"
    },
    "name": "send_packet"
  }
}

Input Schema

NameRequiredDescriptionDefault
cmdYes
rspNo
dataNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior3/5

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

The annotations already declare a non-read-only, open-world, non-destructive write. The description adds a genuine safety constraint beyond them: cmd and data must be replaced together with verified values, and example placeholders must not be sent. It says nothing about response behavior or what rsp toggles.

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?

One compact sentence pair with the warning front-loaded and no filler. Still, much of it is telegraphic shorthand that assumes protocol context.

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?

This is a raw, open-world mutation tool with no output schema and 0% schema coverage, so the description should explain the packet format, the role of rsp, and what a failure looks like. Those gaps remain, leaving an agent with only a warning.

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 0%, so the description needs to carry the parameter meaning and only partially does. It explains that cmd and data form a matched pair with a hex request body, but never explains the hex format or the rsp boolean, the third parameter.

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 names a specific verb and resource: "发送原始 SSO 包(cmd + hex data)". The word "原始" (raw) signals this is a low-level escape hatch, unlike the many high-level send_message and send_image siblings, though no sibling is named directly.

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?

Includes a real audience restriction, "仅供有协议经验的调用方" (only for callers with protocol experience), which narrows when to use it. However, it never names an alternative or states positively when a raw packet is the right choice rather than a structured message tool.

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