recommend_by_budget
依預算和情境推薦台灣商品：送禮、學生、租屋族、居家辦公等。使用者問「X 元送禮推薦什麼」「租屋族該買什麼」「學生 3C 推薦」時使用。
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| scene | No | 可選情境關鍵字，例如「送禮」「租屋」「學生」「露營」「居家辦公」 | |
| budget | Yes | 預算上限（元） | |
| category | No | 可選，指定品類，例如「藍牙耳機」 |
ecpro-mcp
TDQS
A3.8/5.0
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided. The description implies a read-only recommendation operation but does not explicitly state read-only behavior or any side effects. For a tool with no annotations, the description could be more transparent.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness4/5
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is concise, with a single sentence stating the purpose and two example queries. It is front-loaded and easy to parse, though it could slightly benefit from a clearer structure.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness3/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given no output schema, the description does not explain the return format or any additional context. However, for a simple recommendation tool, the core purpose and parameters are sufficiently covered.
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%, so the description adds no extra meaning beyond what the schema already provides. The description's mention of scenarios aligns with the 'scene' parameter but does not enhance understanding of 'budget' or 'category'.
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?
The description clearly states the tool's purpose: recommending Taiwanese products by budget and scenario, with specific examples like gift-giving, students, renters, and work-from-home. It distinguishes itself from sibling tools like search_products or find_deals by focusing on scenario-based recommendations.
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?
The description provides explicit usage examples (e.g., 'X元送禮推薦', '租屋族該買什麼'), helping the agent know when to invoke it. However, it does not specify when not to use it or mention alternatives.
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.7/5.0
Disambiguation4/5
Most tools have clearly distinct purposes, such as price comparison vs. price history vs. store safety. However, there is some overlap between compare_prices, cross_channel_gaps, and price_match_check, which all involve comparing prices across channels. The descriptions help differentiate them, but ambiguity remains for agents.
Naming Consistency3/5
Tool names use snake_case but vary in structure: some start with verbs (compare_prices, find_deals), others with nouns (category_price_range, price_match_check). There is no strict verb_noun pattern, and 'should_i_buy_now' is a full phrase, breaking consistency.
Tool Count4/5
17 tools cover a wide range of e-commerce assistance tasks without being overwhelming. The count is appropriate for the domain, though a few tools (e.g., price_match_check vs. should_i_buy_now) could potentially be merged without losing functionality.
Completeness4/5
The tool set covers most common user needs in Taiwanese e-commerce: product search, price comparison, historical trends, deals, store safety, tech detection, and currency conversion. Missing operations include user-specific features (e.g., watchlist) but the core lifecycle is well-represented.