MAQAMI Travel

put_vouchers_id

Idempotent

Update an existing travel voucher's discount, validity, usage limits, or status by providing its ID and revised fields; used vouchers cannot be changed.

Instructions

Overview

Modify an existing voucher's settings, including discount values, validity periods, usage limits, and status.

When to Use

Extend validity - Update voucher end dates
Adjust discounts - Change discount values or types
Update limits - Modify usage limits or minimum spend
Status changes - Activate or deactivate vouchers

What You Get

Confirmation - Success message when voucher is updated
Updated voucher - Voucher reflects the new settings

Important Notes

Read-only if used - Vouchers that have been used in bookings cannot be modified (returns 404)
All fields required - Must provide all required fields, not just the ones you want to change

Quick Start

Provide the voucher ID and updated fields. Returns confirmation of the update.

Input Schema

TableJSON Schema

Name	Required	Description
`id`	Yes	Unique identifier of the voucher to update
`budget`	No	Total monetary pool the voucher can distribute across all redemptions, in the voucher's currency. If not set or 0, there is no monetary limit and usage is only controlled by usages_limit. When set, budget and usages_limit act as independent limits — whichever is exhausted first will reject the voucher.
`status`	Yes	Updated status of the voucher (e.g., active, inactive)
`currency`	Yes	Currency of the discount
`usages_limit`	Yes	Updated usage limit for the voucher
`validity_end`	Yes	Updated end date of the voucher's validity
`voucher_code`	Yes	A unique code for the new voucher. e.g. manhattan-holidays-100
`discount_type`	Yes	Type of discount, such as percentage or points redemption
`minimum_spend`	Yes	Minimum rate to apply the discount voucher in the voucher currency. e.g. a minimum_spend of USD$100 will only apply for bookings with a price USD$100 or more
`discount_value`	Yes	Value of the discount applied by the voucher. For percentage discounts, a value of 10 represents a 10% discount. For points_redemption, it indicates the fixed amount of points to be redeemed e.g. 10 equals 10 points
`validity_start`	Yes	Updated start date of the voucher's validity
`maximum_discount_amount`	Yes	Maximum discount amount that can be applied using the voucher in voucher currency. e.g. a with a maximum_discount_amount of 50 in USD, will discount from 0 to USD$50

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 28, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already establish readOnly=false, idempotent=true, destructive=false, openWorld=true. The description adds genuinely non-redundant behavior: vouchers already used in bookings cannot be modified and return 404, and the update is a full replace requiring every required field to be resent. That is exactly the kind of state/permission context annotations don't carry.

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?

Front-loaded with an Overview, then scannable sections for when-to-use, return values, and caveats. Sections are short and each carries content; the Quick Start paragraph lightly restates earlier material but does not bloat the definition.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 12-parameter mutation with no output schema, the description covers what it needs to: it explains the return (success confirmation plus the updated voucher), the full-replace semantics, and the 404 constraint on used vouchers. The only omission is routing between this tool and the status-specific sibling.

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

Parameters4/5

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

Schema description coverage is 100%, so the schema documents all 12 parameters and the baseline is 3. The description adds a nuance the schema cannot express: this is a full-replace update where all required fields must be provided, not just the ones being changed, which prevents a partial-update mistake.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (modify) and resource (an existing voucher's settings) and enumerates the modifiable surfaces: discount values, validity periods, usage limits, status. An agent can tell it apart from read siblings like get_vouchers_voucherid, but it does not distinguish itself from the dedicated put_vouchers_id_status sibling even though it claims status changes as a use case.

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 'When to Use' bullets give real context (extend validity, adjust discounts, update limits, status changes), which is better than nothing. However, no when-not conditions are stated and no alternatives are named, and the status-change bullet collides with the put_vouchers_id_status sibling without explaining when to prefer one over the other.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server