Get ManaBuy product detail, SKU list, required order fields, and top-up instructions.
| Name | Required | Description | Default |
|---|---|---|---|
| size | No | ||
| current | No | ||
| urlName | No | Product URL name, for example pubg-mobile-top-up. | |
| productCode | No | ManaBuy product code. |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden of behavioral disclosure. It does explain what data is returned (detail, SKUs, order fields, instructions), but it does not disclose whether authentication is required (sibling login_manabuy suggests it might be), nor does it mention any side effects or limitations. The lack of explicit safety/read-only hints is a gap for a tool that may require auth.
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, well-structured sentence that front-loads the core action and then lists the key output types. Every word adds value, and there is no redundancy or unnecessary detail.
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?
The description gives a good sense of the tool's outputs, but it lacks operational context such as whether login is required (sibling login_manabuy implies this), how pagination parameters work, or how to choose between urlName and productCode. With no output schema and no annotations, this is a noticeable gap, but the tool's purpose is still clear enough for minimal use.
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 provides descriptions for urlName and productCode (50% coverage), but the tool description adds no additional parameter meaning. It does not explain how the parameters map to the product being fetched, nor does it clarify the role of size and current (likely pagination). With 50% schema coverage, the description should compensate but does not.
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 clearly states the tool's function with a specific verb ('Get') and resource ('ManaBuy product detail'), and enumerates the key outputs (SKU list, required order fields, top-up instructions). This distinguishes it from siblings like search_products (which presumably searches) and create_order (which creates orders).
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: use this tool when you need product detail, SKU list, or top-up instructions. It does not explicitly name alternative tools or state when not to use it, but the context is sufficiently clear given the sibling tool names. No exclusions or prerequisites are mentioned.
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.
Each tool targets a distinct action or resource: auth (login/logout/status), product discovery (search/detail), ordering (quote/create/status/detail). There is no functional overlap that would cause an agent to select the wrong tool.
All tool names follow a consistent verb_noun pattern in snake_case, such as search_products, create_order, get_login_status. Even login_manabuy and logout_manabuy fit the pattern with the domain as the object.
With 9 tools, the server is well-scoped for the ManaBuy ordering domain. Each tool covers a necessary step in the workflow without redundancy or bloat.
The set covers product discovery, quoting, order creation, order status/detail tracking, and session management. A notable gap is the lack of a cancel order or list orders capability, but the core purchasing flow is complete.
