Skip to main content
Glama

get_sales_analytics

Retrieve Xianyu sales statistics for a chosen number of days to track performance and identify sales trends.

Instructions

获取销售统计

Args: days: 统计天数

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

Input Schema

NameRequiredDescriptionDefault
daysNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.3/5.0
Behavior1/5

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

No annotations are supplied, so the description carries the full disclosure burden, and it discloses nothing: not whether this is read-only, what permissions are needed, what the time window is anchored to, or whether the numbers are aggregated or raw. "Returns: 销售统计数据" merely restates the tool name.

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?

It is short and front-loaded, so nothing is wasted, but the brevity comes from under-specification rather than economy. The Args/Returns scaffolding is boilerplate that conveys nearly no information.

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?

With no annotations and no output schema, the description is the only place an agent could learn what the response looks like or how it is scoped, and it does not. For an analytics tool whose value depends on granularity and aggregation semantics, this leaves a substantial gap.

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 coverage is 0%, so the description must compensate, and it does so only partly: "days: 统计天数" confirms the parameter is a day-count window, but gives no units beyond implicit days, no valid range, no timezone, and no statement that omitting it defaults to 7.

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

Purpose3/5

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

"获取销售统计" names a verb and resource, so the basic intent is legible. But it draws no boundary against the analytics siblings (get_item_analytics, get_traffic_analytics, get_top_items), so an agent cannot tell from the text which of these returns what.

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 at all: no statement of which questions this answers, no exclusions, and no pointer to an alternative tool. The agent must infer the choice entirely from the sibling names.

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