Skip to main content
Glama

generate_report

Generate a multi-day analysis report for Xianyu product and conversation data, summarizing key metrics over a specified period for review.

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

Input Schema

NameRequiredDescriptionDefault
daysNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.5/5.0
Behavior2/5

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

With no annotations supplied, the description carries the entire behavioral burden and does very little: it does not say whether this is a read-only aggregation, whether it is expensive or slow, whether results are cached, whether it requires permissions, or over what data the analysis runs. The "Returns: 报告数据" line restates that a report is returned without describing its shape or granularity.

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, but the Args/Returns scaffolding consumes half the space while adding almost nothing — the Returns section is tautological ("report data"). It is under-specified rather than efficiently concise.

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 report-generation tool with no annotations and no output schema, the description should explain what analysis is produced, whether any state is created, and roughly what the report contains. None of that is present, leaving the agent unable to predict the result or cost of the call.

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 for the single 'days' parameter. It does clarify that 'days' is the statistical window (统计天数), which adds modest meaning beyond the bare integer schema, but it omits the default of 7, any bounds, and what a larger window changes in the output.

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?

The description gives a generic verb+resource ("generate comprehensive analysis report"), which tells the agent it produces a report, but "comprehensive analysis" is too vague to distinguish it from siblings like get_sales_analytics, get_traffic_analytics, or get_item_analytics. Nothing indicates what data or dimensions the report covers.

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 mention of when to prefer this over the analytics sibling tools, and no prerequisites or exclusions. The only hint is the presence of a 'days' argument, which implies a time-window aggregation but is never stated as a usage rule.

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