Retrieve the category tree to obtain category_id required for posting products on Shopee.
Lấy cây danh mục — cần trước khi đăng bài để có category_id.
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": "get_category"
}
}| Name | Required | Description | Default |
|---|---|---|---|
| language | No |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description bears full responsibility for behavioral disclosure. It states the tool retrieves a category tree, implying a read-only operation, but it does not mention potential limitations like pagination, caching, or rate limits. For a simple read operation, the transparency is adequate but not explicit.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single sentence that front-loads the action and then provides context. It is concise and to the point. However, it could be slightly improved by including parameter details, which would make it more useful without sacrificing brevity.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the lack of an output schema, the description should at least hint at what the tool returns (e.g., a tree structure of categories). It does not. Additionally, parameter semantics are missing. The description covers purpose and usage but leaves significant gaps in completeness for a tool with low complexity.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The input schema has one parameter (language) with no description, and the tool description does not mention or explain it at all. With 0% schema description coverage, the description fails to compensate by adding meaning to the parameter, leaving the agent without guidance on its purpose or allowed values.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description uses a specific verb 'Get' and resource 'category tree', clearly stating its purpose of retrieving the category tree and explicitly noting it is needed before posting to obtain category_id. This distinguishes it from sibling tools like add_item or get_item_list.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description clearly indicates when to use this tool: before posting to get category_id. While it does not explicitly list alternatives or when not to use, the context is clear and sufficient for an agent to understand its role in the workflow.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.