Skip to main content
Glama

get_unread_messages

Retrieve the current unread message count and status from Xianyu, so you can check for new buyer inquiries without opening each conversation.

Instructions

获取未读消息数

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_unread_messages"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3/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 behavioral burden. It only implies a read via '获取', but says nothing about required auth or account context, whether results are account-wide or scoped, or the concrete shape of '未读消息状态'. For a zero-annotation tool that gap is meaningful, especially since there is no output schema to fall back on.

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 short lines with the purpose front-loaded; nothing is padded. The only weak element is the 'Returns:' line, which occupies space while conveying a vague notion of status rather than anything actionable.

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 simple zero-parameter read call, but because there are no annotations and no output schema, the description is the sole source of truth for the return value, and it is inconsistent between 'count' and 'status'. An agent cannot tell whether it receives an integer, a per-conversation breakdown, or flags, which is the one thing this tool most needs to specify.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes no parameters, so there is nothing for the description to disambiguate. Baseline 4 applies; no parameter meaning is missing.

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 states a specific verb and resource ('获取未读消息数'), which lets an agent distinguish this from the message-listing sibling get_messages. The purpose is readable at a glance, though the second line's '未读消息状态' (status) sits slightly at odds with 'count', introducing minor ambiguity about what is actually returned.

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 guidance on when to call this instead of get_messages or get_conversations, and no stated preconditions. The agent must infer usage from the name alone, and the description does nothing to route it among the several 'get_*' siblings.

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