Skip to main content
Glama

search_market_sales

检索药品销量(2016–2024)。channel:drug=药品汇总(46 万行)、hospital=医院端(133 万行)、network=线上电商(京东/天猫/抖音,36 万行)、all=三张表合并。⚠️ 必须带 drug 或 company;库内没有线下连锁药店动销。

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

Input Schema

NameRequiredDescriptionDefault
drugNo药品名
yearNo单一年份
limitNo返回条数,默认 20,硬上限 20(超出自动压低)
offsetNo翻页偏移,默认 0;offset+limit 不得超过 1000
channelNoall / drug / hospital / network,默认 all
companyNo企业名
year_toNo截止年
provinceNo省份/地区关键词
year_fromNo起始年

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / limit / description
      Previous value: -"返回条数,默认 20,硬上限 50(超出自动压低)"New value: +"返回条数,默认 20,硬上限 20(超出自动压低)"
    • changedInput schema / properties / offset / description
      Previous value: -"翻页偏移,默认 0"New value: +"翻页偏移,默认 0;offset+limit 不得超过 1000"
  2. First observed

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses data coverage (2016–2024), per-channel row counts (46万/133万/36万), merge behavior for 'all', and a required-filter constraint. It omits return format, pagination interaction, and any auth/rate-limit context.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loads purpose, then packs channel semantics and the ⚠️ critical constraint into minimal text with zero filler. Every clause earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Covers purpose, scope, channels, and the key filter constraint for a 9-param tool with no output schema. Return shape and limit/offset interplay are left to the schema, which is acceptable, but the description could say a bit more about result semantics.

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?

Schema coverage is 100%, so baseline is 3; the description earns above that by explaining what each channel value actually contains (aggregate vs hospital vs online e-commerce, with row counts) and by stating the drug/company requirement, which the schema does not encode.

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

Purpose5/5

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

States a specific verb+resource (检索药品销量) with an explicit date scope (2016–2024). No sibling tool covers market sales, so it is unambiguously distinguishable from search_drugs/search_companies and the rest.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives a hard usage prerequisite (必须带 drug 或 company) and an explicit when-not boundary (库内没有线下连锁药店动销), plus channel selection guidance. It stops short of naming an alternative tool to use instead, so it falls just under 5.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.