nuvemshop_coupons
Read-onlyIdempotent
Lista cupons de desconto da loja Nuvemshop (params opcionais: page, per_page).
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| page | No | ||
| account | No | ||
| per_page | No |
Nuvemshop
TDQS
B3.2/5.0
Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already provide readOnlyHint and idempotentHint, indicating safe reads. The description adds little beyond mentioning optional params; it does not disclose pagination behavior, rate limits, or return format.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness4/5
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single concise sentence that front-loads the core purpose. It has no wasted words, though it could be slightly expanded for completeness.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness2/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given 3 undocumented parameters, no output schema, and low schema coverage, the description is too brief. It does not explain pagination, the role of 'account', or expected output structure.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters2/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 0%, so the description must compensate. It only mentions 'page' and 'per_page' as optional, missing the 'account' parameter entirely, and provides no semantic details about any parameter's purpose or format.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose5/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description 'List discount coupons from the Nuvemshop store' uses a specific verb ('List') and resource ('discount coupons'), clearly distinguishing it from the sibling write tool 'nuvemshop_coupons_write_create'.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines3/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies it is for reading coupons, but it does not explicitly state when to use this tool versus the write alternative, nor does it mention any prerequisites or context.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Try in Browser
Glama MCP Gateway
Add one secure layer between your agents and this server.
TDQS
C2.6/5.0
Disambiguation2/5
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.
Naming Consistency2/5
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.
Tool Count2/5
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.
Completeness3/5
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.