Skip to main content
Glama
code-rabi

Mews MCP

by code-rabi

addVouchers

Create discount codes and gift certificates in the Mews hospitality platform to manage promotional offers and customer incentives.

Instructions

Adds new vouchers (discount codes, gift certificates) to the system

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
VouchersYesArray of voucher objects to create

Implementation Reference

  • The asynchronous execute function implementing the core logic of the addVouchers tool. It constructs the request data from input arguments and calls the mewsRequest utility to POST to the '/api/connector/v1/vouchers/add' endpoint.
    async execute(config: MewsAuthConfig, args: unknown): Promise<ToolResult> {
      const inputArgs = args as Record<string, unknown>;
      const requestData = {
        ...inputArgs
      };
    
      const result = await mewsRequest(config, '/api/connector/v1/vouchers/add', requestData);
      return {
        content: [{
          type: 'text',
          text: JSON.stringify(result, null, 2)
        }]
      };
    }
  • The inputSchema defining the expected input structure for the addVouchers tool, specifying an array of Vouchers with required fields Name and Code, and optional fields like Value, validity dates, usage limits, etc.
    inputSchema: {
      type: 'object',
      properties: {
        Vouchers: {
          type: 'array',
          items: {
            type: 'object',
            properties: {
              Name: { type: 'string', description: 'Voucher name' },
              Code: { type: 'string', description: 'Voucher code' },
              Value: {
                type: 'object',
                properties: {
                  Currency: { type: 'string', description: 'Voucher currency' },
                  Amount: { type: 'number', description: 'Voucher amount' }
                },
                description: 'Voucher value'
              },
              ValidityStartUtc: { type: 'string', description: 'Voucher validity start (ISO 8601)' },
              ValidityEndUtc: { type: 'string', description: 'Voucher validity end (ISO 8601)' },
              UsageLimit: { type: 'number', description: 'Maximum number of uses' },
              Type: { type: 'string', description: 'Voucher type' },
              AccountingCategoryId: { type: 'string', description: 'Accounting category for voucher' }
            },
            required: ['Name', 'Code']
          },
          description: 'Array of voucher objects to create'
        }
      },
      required: ['Vouchers'],
      additionalProperties: false
    },
  • Import statement bringing the addVouchersTool into the central index file.
    import { addVouchersTool } from './vouchers/addVouchers.js';
  • The addVouchersTool is added to the allTools array, which collects and exports all available tools for registration and execution.
    // Voucher tools
    addVouchersTool,
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states 'Adds new vouchers' which implies a write operation, but fails to mention critical details like required permissions, whether it's idempotent, error handling, or rate limits. This leaves significant gaps in understanding how the tool behaves.

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?

The description is a single, efficient sentence that front-loads the core action and resource, with no wasted words. It's appropriately sized for its purpose, making it easy to parse quickly.

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 the complexity of a write operation with no annotations and no output schema, the description is insufficient. It doesn't cover behavioral aspects like side effects, response format, or error conditions, leaving the agent with incomplete context for safe and effective use.

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?

The schema description coverage is 100%, so the schema fully documents the single parameter 'Vouchers' and its nested properties. The description adds no additional meaning beyond implying bulk addition ('vouchers' plural), which aligns with the schema but doesn't provide extra semantic context. This meets the baseline for high schema coverage.

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?

The description clearly states the action ('Adds') and resource ('new vouchers') with clarifying examples ('discount codes, gift certificates'), making the purpose evident. However, it doesn't differentiate from sibling tools like 'addPayment' or 'addLoyaltyMemberships' beyond the resource type, which prevents a perfect score.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives, such as whether it's for bulk creation or single entries, or any prerequisites like authentication. It lacks explicit context or exclusions, leaving usage ambiguous.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/code-rabi/mews-mcp'

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