Skip to content
AsklearAgent Docs
Dashboard
中EN

Shop performance by name

Resolve one spoken shop name and query its monthly atomic metrics.

Document ID: agent.dataset.jd.task.shop_name_performance

Authenticated runtime tools and each query response are authoritative for tenant scope and current data coverage.

This is an MCP query composition, not a complete business report; see Research Methods in the Agent Docs for complete workflows.

Required inputs

shopRequired · search_values

Spoken or exact shop name

shop
timeRequired · user_required

Analysis time range

Execution steps

  1. 1
    resolve_shop · search_values

    Resolve the spoken shop name.

    Request contract
    shop ← $shop
  2. 2
    query_trend · query_metrics

    Query shop metrics grouped by month.

    Request contract
    metrics: gmv, units, aspgroup_by: shop, monthfilter: shop eq $shoptime: $time

Call example

Replace example values with exact user inputs or platform values returned by search_values.

search_values
{
  "dataset": "jd",
  "field": "shop",
  "kw": "示例店铺",
  "limit": 10,
  "task_query": "使用 jd 数据执行按店铺名查询销售表现；shop=示例店铺，time={\"last_complete_months\":3}"
}
query_metrics
{
  "dataset": "jd",
  "filters": [
    {
      "field": "shop",
      "op": "eq",
      "value": "示例店铺"
    }
  ],
  "group_by": [
    "shop",
    "month"
  ],
  "metrics": [
    "gmv",
    "units",
    "asp"
  ],
  "task_query": "使用 jd 数据执行按店铺名查询销售表现；shop=示例店铺，time={\"last_complete_months\":3}",
  "time": {
    "last_complete_months": 3
  }
}

Output policy

  • Present the resolved shop name and month-by-month trend with metric definitions.

Stop conditions

  • Stop and ask when the shop-name match is ambiguous.

Limitations

  • Do not infer traffic, inventory, or operational causes.