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: cancel]
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?
Annotations are neutral. Description states 'transition de status' but doesn't elaborate on irreversibility or side effects. Adequate but not detailed beyond required fields and bulk execution.
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?
Description mixes multiple actions (update, close, etc.) before focusing on cancel, which is slightly cluttered. Could be more streamlined for the cancel 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?
Given no output schema and 0% schema coverage, description covers action, parameters, and bulk support. Lacks return value details or prerequisites but is sufficient for cancel operation.
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 0%, but description clarifies parameters: order_id required, data optional with example (reason), and order_ids for bulk. Adds meaning beyond raw 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 specifies the tool cancels a Nuvemshop order, clearly differentiating from sibling tools like close, open, etc. The flattened action 'cancel' makes the purpose unambiguous.
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?
It describes the cancel action as a status transition, requires order_id, and notes optional data like reason. Bulk support is mentioned. Lacks explicit when-not-to-use but context with siblings provides clarity.
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.