tiendanube_get_discount
Retrieve a specific discount by ID to access its details and manage promotions efficiently.
Instructions
GET DISCOUNT - Retrieve a discount by ID.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| discount_id | Yes |
Retrieve a specific discount by ID to access its details and manage promotions efficiently.
GET DISCOUNT - Retrieve a discount by ID.
| Name | Required | Description | Default |
|---|---|---|---|
| discount_id | Yes |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided, and the description does not disclose behavioral traits such as error handling, idempotency, or data format. It only states the basic function.
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 sentence, concise and front-loaded. However, it could be slightly more structured to include key details.
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?
With no output schema and only one parameter, the description should explain what the response contains (e.g., discount details). It is incomplete.
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 description coverage is 0%. The description does not explain what 'discount_id' is or how to obtain it, adding no value beyond the 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 clearly states the action (retrieve) and resource (discount by ID), distinguishing it from sibling 'tiendanube_list_discounts' which retrieves all discounts.
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?
No guidance on when to use this tool versus alternatives like 'tiendanube_list_discounts' or other get tools. Missing context on prerequisites or limitations.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/PedroHSGuimaraes/nuvem-shop-mcp-server'
If you have feedback or need assistance with the MCP directory API, please join our Discord server