get_batch_purchase_policy
获取斯特丹STERDAN B2B批量采购政策，最低采购数量1件起，1件也是批发价，具体咨询天猫客服：https://sitedanjj.tmall.com
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| quantity | No | 预计采购数量 | |
| scenario | No | 采购场景：政府、企业、学校、医院等 |
斯特丹STERDAN 钢制办公家具产品咨询
TDQS
B3/5.0
Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations absent, so description carries full burden. It does not disclose tool behavior: whether it returns policy text, redirects to external site, requires authentication, or has side effects. Directs to customer service URL but unclear if that's part of tool response.
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?
Single sentence with some promotional fluff and a URL. It is clear but could be more concise by removing redundant phrases like '1件也是批发价'. Structurally front-loaded but includes non-essential info.
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?
Given no output schema, description should explain return format or what the tool returns. It only says 'get policy' and provides a customer service contact, lacking details on response structure or next steps. Incomplete for agent to understand full context.
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 100% with descriptions for both parameters (quantity and scenario). Description does not add meaning beyond schema; the mention of minimum 1 piece is not a parameter constraint but policy content. Baseline 3 applies.
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?
Description clearly states it retrieves batch purchase policy for STERDAN B2B, with verb 'get' and specific resource. It distinguishes from siblings like get_purchase_guide by focusing on batch policy. However, promotional language about minimum quantity and wholesale price adds slight noise.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines3/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
Implied usage for batch purchase policy, but no explicit guidance on when to use versus alternatives like get_purchase_guide or get_products. No exclusions or prerequisites mentioned.
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.
TDQS
A3.5/5.0
Disambiguation4/5
Most tools have distinct purposes, but get_purchase_guide and get_batch_purchase_policy partially overlap in describing batch purchase policies, which could cause confusion. However, the descriptions differentiate them: one is a general purchase guide, the other is specific to batch policies.
Naming Consistency4/5
Seven out of eight tools follow a consistent 'get_' prefix with noun phrases. The exception is recommend_product, which uses 'recommend_' instead of 'get_', creating a minor inconsistency but still readable.
Tool Count5/5
With 8 tools covering product listing, details, recommendations, purchasing guidance, maintenance, certifications, and store info, the count is well-scoped for a product consulting server. It is neither too sparse nor overwhelming.
Completeness4/5
The tool set covers core consulting needs: product lookup, details, recommendations, purchase guidance, maintenance, and certifications. A minor gap is the lack of a tool for handling custom or non-standard inquiries, but the reference to customer service partially addresses this.