convert_price
把台幣金額換算成美金、日圓、人民幣等主要外幣（即時匯率）。使用者問「這個多少美金／日圓」「跨境比價」時使用。
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| amount_twd | Yes | 台幣金額 |
ecpro-mcp
TDQS
A3.6/5.0
Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description claims conversion to major currencies but does not specify how the target currency is selected (no parameter for it). The input schema only includes 'amount_twd', leaving ambiguity about whether the tool returns all currencies or only one. No annotations are provided to clarify safety or behavior.
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?
The description is two sentences, immediately front-loading the purpose and usage context. Every word earns its place, with no wasted text.
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?
No output schema is provided, and the description does not explain what the tool returns (e.g., conversion result, list of currencies). The ambiguity about target currency selection makes it incomplete for a straightforward conversion tool.
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 a clear description for 'amount_twd' ('台幣金額'). The tool description adds that it is the amount to convert, but no further semantics like bounds or validation. Score at baseline as schema already documents the parameter.
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 converts TWD to major foreign currencies (USD, JPY, RMB) using real-time exchange rates. It distinguishes itself from sibling tools, which are e-commerce and price comparison focused.
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 explicitly tells when to use the tool: when users ask 'how much in USD/JPY' or for cross-border price comparison. It does not explicitly mention when not to use, but the context is clear and no alternative tools are provided.
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.