Generate the current 2FA/TOTP code (6 digits) from a Base32 secret key (Google Authenticator style). Sinh mã 2FA/TOTP hiện tại (6 số) từ khóa bí mật Base32. Tính toán cục bộ, không lưu, không gửi đi đâu.
| Name | Required | Description | Default |
|---|---|---|---|
| secret | Yes | Base32 secret key (spaces allowed). Khóa bí mật Base32 (cho phép có dấu cách). |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
A key behavioral trait is explicitly disclosed: computation happens locally, the secret is not stored, and nothing is transmitted elsewhere. This is important privacy/security context, especially since no annotations are provided. The description does not cover error handling or time-step behavior, but the core non-obvious guarantee is present.
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 compact and front-loaded, leading with the action, output, and input requirement, then adding the critical privacy guarantee. The bilingual content adds some repetition but is not filler and serves the intended audience.
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 single-parameter tool with no output schema, the description gives enough information: what input is needed, what output to expect, and how the operation behaves. An agent can select and invoke this tool correctly. Minor details like invalid-secret error behavior are not covered, but they are not essential for basic usage.
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 schema already documents the secret parameter with type, required status, and the note that spaces are allowed. The description restates 'Base32 secret key' and adds 'Google Authenticator style', but does not significantly extend the parameter semantics beyond the schema. With 100% schema coverage, the baseline 3 is appropriate.
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 and resource: generate the current 2FA/TOTP code from a Base32 secret key. It also clarifies the output format (6 digits) and style (Google Authenticator). The sibling tools are all commerce-related, so this tool is immediately distinguishable.
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 tool describes exactly when it should be used: when a current TOTP/2FA code is needed from a Base32 secret. It does not mention exclusions or alternatives, but none of the sibling tools perform a comparable function, so the usage context is clear enough.
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.