rebate_rate_stats
当前有效出口退税率分布概览。
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
china-export-rebate-mcp
TDQS
B3.1/5.0
Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden. It mentions 'current valid' as a filter, but does not disclose whether the operation is read-only, what the aggregation logic is, or any limitations. The description is too minimal to provide meaningful behavioral transparency.
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 a single short sentence with no filler. It is concise, front-loaded, and contains no unnecessary information.
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?
Without an output schema, the description should clarify what the distribution overview contains (e.g., buckets, counts, percentages). It only states the general concept, leaving ambiguity about the return value structure and available breakdowns.
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?
The tool accepts zero parameters, so the schema fully covers the parameter space. The description does not need to explain parameters, and the baseline for 0-parameter tools 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?
The description states '当前有效出口退税率分布概览' (overview of current effective export rebate rate distribution), which identifies the resource and output type. It implies differentiation from sibling tools that query specific rates or search by name, though not explicitly.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines2/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance is provided on when to use this tool versus query_rebate_rate or search_rebate_by_name. The description implies an aggregate use case, but there is no explicit context, prerequisites, or exclusions.
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.8/5.0
Disambiguation5/5
Each tool has a clearly distinct purpose: one queries by HS code, one searches by product name, and one provides statistical overview. There is no overlap or ambiguity between them.
Naming Consistency4/5
Two tools follow a verb_noun pattern (query_rebate_rate, search_rebate_by_name), but rebate_rate_stats uses only nouns. This minor deviation is easy to understand but breaks the otherwise consistent pattern.
Tool Count5/5
With 3 tools, the server is well-scoped for its purpose of querying China export rebate rates. Each tool covers a distinct and necessary function without redundancy.
Completeness4/5
The core operations of querying by HS code and by product name are covered, plus a useful statistical overview. There is no obvious missing functionality for a read-only rebate rate lookup service, though a list-all option could be an enhancement.