karrito-mcp

create_discount

Define discount codes with percentage or fixed value, set expiration and usage limits to manage promotions in your store.

Create a new discount code for your Karrito store. Requires KARRITO_API_KEY environment variable.

TableJSON Schema

Name	Required	Description
`code`	Yes	Discount code (e.g., VERANO20)
`type`	Yes	Discount type: percentage (e.g., 20%) or fixed amount (e.g., $5 off)
`value`	Yes	Discount value (percentage 0-100 or fixed amount in store currency)
`maxUses`	No	Maximum number of times this discount can be used
`expiresAt`	No	Expiration date in ISO 8601 format (e.g., 2026-12-31T23:59:59Z)
`minOrderAmount`	No	Minimum order amount required to use this discount

B3.4/5.0

Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations; description only mentions env var. Missing: idempotency, uniqueness of code, return value, side effects.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, minimal waste, front-loaded with purpose.

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?

No output schema; description fails to explain return value or validation behavior. Incomplete for a creation tool with 6 params.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage 100% with descriptions; description adds no extra param context. Baseline 3.

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?

Clear verb+resource: 'Create a new discount code'. Distinguishes from siblings (list, update, delete) by action.

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?

No explicit when-to-use vs alternatives; only a prerequisite (KARRITO_API_KEY). Agent relies on tool name for intent.

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/curetcore/karrito-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server