Skip to main content
Glama

get_sendable_conversations

Retrieve conversations that can receive messages on Xianyu, with an optional limit and context pre-warming. Use it to pick valid chat targets before sending messages.

Instructions

获取可发送会话列表

Args: limit: 返回数量限制 warm_context: 是否尝试预热前几个会话的商品上下文

Returns: 可发送会话列表和状态

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

Input Schema

NameRequiredDescriptionDefault
limitNo
warm_contextNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description carries the full burden of behavioral disclosure and does not state that this is a read operation, whether warm_context has side effects or latency cost, or what permissions are required. It does at least mention a returned 'status', but gives no detail on failure modes or rate limits.

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?

Compact docstring with an Args block and a Returns line, front-loading the purpose in the first sentence. No filler, though the Args/Returns scaffolding is minimal and the Returns line adds little.

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?

For a two-parameter list tool with no annotations and no output schema, the description leaves important gaps: what qualifies a conversation as 'sendable', how results are ordered or paginated, and whether warming has costs. The one-line Returns statement is too thin to substitute for an output schema.

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 0%, so the description must compensate; it explains both parameters, notably that warm_context pre-warms product context for the first few conversations, which is real meaning beyond the bare schema titles. However, 'first few' is vague, limit has no documented range, and the interaction between limit and warm_context is unstated.

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 ('获取可发送会话列表' – get the list of sendable conversations), which is more precise than a generic conversation listing because of the 'sendable' qualifier. It does not, however, say how this differs from the sibling get_conversations, so the agent cannot fully disambiguate without inspecting both.

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?

No when-to-use guidance, no prerequisites, and no mention of alternatives such as get_conversations or send_message. The name implies the tool is used to find conversations you can message, but that inference is left entirely to the agent.

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