Skip to main content
Glama

send_message

Send a message to a specified Xianyu user by user ID and message content, returning the send result for buyer or seller communication.

Instructions

发送消息

Args: user_id: 用户 ID content: 消息内容

Returns: 发送结果

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": {
      "user_id": "<user_id>",
      "content": "<content>"
    },
    "name": "send_message"
  }
}

Input Schema

NameRequiredDescriptionDefault
contentYes
user_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden, yet it discloses nothing about permissions, message length or rate limits, whether the send is idempotent, delivery failure behavior, or side effects. The only hint is a one-line "Returns: 发送结果" (send result), which conveys no real information about the response shape.

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

Conciseness3/5

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

The text is short and front-loaded with the action, so it is not bloated in absolute terms. However, the Args/Returns boilerplate duplicates the schema verbatim and earns no space, leaving the description terse without being informative.

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

Completeness1/5

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

For a two-parameter mutation tool with no annotations, no output schema, and 0% schema coverage, the description supplies none of the missing context. An agent could not confidently call this tool correctly, or predict what happens on failure, from this definition alone.

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?

Both parameters have 0% schema description coverage, and the Args block merely repeats the property names in Chinese (user_id: 用户 ID, content: 消息内容) without explaining where the user_id comes from, whether it is a platform-scoped ID, or any constraints on content. No meaning is added beyond the bare schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description says "发送消息" (send a message), which is a verb+resource but is essentially a restatement of the tool name send_message. It gives no indication of scope, target channel, or how it differs from siblings such as get_messages, get_unread_messages, or get_sendable_conversations.

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, no prerequisites, and no mention of alternatives. An agent must guess whether this sends to an existing conversation, a raw user_id, or something else, and cannot tell from the text when to prefer it over the sibling messaging tools.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.