Mutações em pedidos Nuvemshop. Ações:
update: PUT no pedido (requer order_id; data = JSON com campos editáveis, ex. owner_note).
close | open | cancel | pack | fulfill: transição de status (requer order_id; data opcional, ex. cancel aceita { reason }).
[Flattened action: pack]
Bulk support: accepts order_ids for batched execution.
| Name | Required | Description | Default |
|---|---|---|---|
| data | No | ||
| account | No | ||
| order_id | Yes | ||
| order_ids | No |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description discloses that the tool performs write operations (mutations) and supports bulk execution via order_ids. However, it does not elaborate on side effects, such as whether packing triggers downstream actions. Annotations (all false) are consistent but provide no extra context.
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 uses bullet points and separates actions, but it is somewhat verbose and in Portuguese. It could be more concise by focusing on the pack action and omitting other actions, or by clarifying that this is a combined tool.
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 tool has no output schema, yet the description does not mention return values or error handling. It lacks prerequisites, authentication needs, and details on bulk execution behavior. For a write tool with multiple actions, more completeness is needed.
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 description explains order_id (required) and order_ids (for bulk) but does not describe the 'account' parameter present in the schema. For 'data', it gives examples for update and cancel but not specifically for pack. With 0% schema coverage, the description partially compensates but misses the account field.
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 lists multiple actions (update, close, open, cancel, pack, fulfill) but the tool name specifies 'pack', causing confusion about the tool's primary purpose. It indicates that this tool handles mutations and specifically mentions 'Flattened action: pack', but does not clearly differentiate from sibling tools dedicated to single actions.
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 states required parameters for each action but does not explicitly guide when to use this tool versus individual sibling tools like nuvemshop_orders_write_cancel. There is no explanation of when packing is appropriate or when to prefer the combined tool.
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.
Many tools have overlapping functionality, especially the get/list pairs for customers, orders, and products which have identical descriptions except for the default action. The multiple order write tools (cancel, close, fulfill, etc.) also share the same underlying description, making it difficult for an agent to select the correct one.
Tool names mix patterns: some use simple <resource> (nuvemshop_categories), others use <resource>_<action> (nuvemshop_customers_get), and others use <resource>_write_<action> (nuvemshop_orders_write_cancel). The get/list split for customers, orders, and products is inconsistent with the categories tool which lacks such a split.
With 24 tools, the server has an excessive number for its scope. Many tools are redundant (e.g., separate get and list tools for each resource, and individual write tools for order status transitions). Consolidating these would reduce the count and improve usability.
The server covers the main e-commerce resources (categories, coupons, customers, orders, products) with read and write operations. However, there are gaps: no ability to create or delete customers, delete products, or delete coupons. The set is workable but not fully comprehensive.