Get your account balance and level (requires your shop api_key). Xem số dư & hạng tài khoản của bạn (cần api_key của tài khoản shop). Trả balance (VND), level, discount.
| Name | Required | Description | Default |
|---|---|---|---|
| api_key | Yes | Your shop account API key. Khóa API tài khoản shop của bạn (Trang cá nhân → API). |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the burden of behavioral disclosure. It does communicate the authentication requirement and the return payload ('Trả balance (VND), level, discount'), but it does not explicitly state that the operation is read-only, how errors such as an invalid key are handled, or any rate-limit concerns. This is adequate but not comprehensive.
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 short and front-loaded with the essential action and prerequisite. The bilingual Vietnamese text repeats the same information, which is slightly redundant for English readers but may serve a target audience. Overall it is efficient with minimal waste.
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?
For a simple one-parameter tool with no output schema, the description is largely complete: it states the purpose, the required input, and the return fields (balance, level, discount). It does not explain how the returned discount is applied, but that is beyond the core need for invoking the tool correctly.
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?
Schema coverage is 100%, so the baseline is 3. The schema already documents api_key and where to find it ('Trang cá nhân → API'), and the description merely reiterates that the key is required. No additional semantic meaning is added beyond the schema.
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 states a specific verb ('Get'), a clear resource ('your account balance and level'), and even lists the returned fields (balance, level, discount). This makes it plainly distinct from sibling tools like get_2fa or get_product, so an agent can select it correctly without confusion.
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 provides clear context for when to use the tool: whenever you need your own account balance or level, and the prerequisite that your shop api_key is required. It does not explicitly name alternatives or exclusions, but the purpose is so self-contained that the usage context is clear enough for an agent.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Product discovery tools such as best_sellers, latest_products, recommend_products, and similar_products have related listing purposes and could be confused, though descriptions clarify sorting and filtering criteria. Social-check tools also overlap: check_live_facebook, deep_inspect, and check_health_bulk can all verify Facebook accounts. Most tools are distinct, but the boundaries are not always crisp.
The dominant convention is snake_case verb_noun, e.g. buy_product, search_products, list_categories, check_order_status. A few names deviate, such as best_sellers, latest_products, similar_products, how_to_start, and deep_inspect, but they are still readable and predictable.
With 19 tools, the set falls into the 16-25 heavy range and could be trimmed: there are nine product-listing/search/recommend tools and three overlapping social-check tools. The count is not extreme, and the combined commerce-plus-verification scope is covered, but it feels heavier than necessary.
The core commerce workflow is complete: discover products, quote, confirm purchase, check order status, and view balance. Minor gaps include no order-history tool, no cancellation tool, and no actual top-up execution, but these are workaroundable for the stated shop purpose.