Skip to main content
Glama
code-rabi

Mews MCP

by code-rabi

addReservation

Create new reservations in Mews hospitality platform by specifying customer, service, dates, and booking details to manage hotel bookings.

Instructions

Adds a new reservation with the specified details

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
CustomerIdNoCustomer ID for the reservation
ServiceIdYesService ID
RatePlanIdYesRate plan ID
StartUtcYesCheck-in date/time (ISO 8601)
EndUtcYesCheck-out date/time (ISO 8601)
VoucherCodeNoDiscount voucher code
BookingChannelNoChannel for booking
NotesNoReservation notes
SpaceCategoryIdNoSpace category ID
AdultCountNoNumber of adults
ChildCountNoNumber of children

Implementation Reference

  • Handler (execute function) for 'addReservation' tool that sends a POST request to the Mews reservations/add endpoint using the mewsRequest utility.
    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/reservations/add', requestData);
      return {
        content: [{
          type: 'text',
          text: JSON.stringify(result, null, 2)
        }]
      };
    }
  • Input schema defining the parameters accepted by the addReservation tool, with required fields ServiceId, RatePlanId, StartUtc, EndUtc.
    inputSchema: {
      type: 'object',
      properties: {
        CustomerId: {
          type: 'string',
          description: 'Customer ID for the reservation'
        },
        ServiceId: {
          type: 'string',
          description: 'Service ID'
        },
        RatePlanId: {
          type: 'string',
          description: 'Rate plan ID'
        },
        StartUtc: {
          type: 'string',
          description: 'Check-in date/time (ISO 8601)'
        },
        EndUtc: {
          type: 'string',
          description: 'Check-out date/time (ISO 8601)'
        },
        VoucherCode: {
          type: 'string',
          description: 'Discount voucher code'
        },
        BookingChannel: {
          type: 'string',
          description: 'Channel for booking'
        },
        Notes: {
          type: 'string',
          description: 'Reservation notes'
        },
        SpaceCategoryId: {
          type: 'string',
          description: 'Space category ID'
        },
        AdultCount: {
          type: 'number',
          description: 'Number of adults'
        },
        ChildCount: {
          type: 'number',
          description: 'Number of children'
        }
      },
      required: ['ServiceId', 'RatePlanId', 'StartUtc', 'EndUtc'],
      additionalProperties: false
    },
  • Import of the addReservationTool for inclusion in the tools registry.
    import { addReservationTool } from './reservations/addReservation.js';
  • Registration of addReservationTool in the allTools array exported for use across the application.
    addReservationTool,
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. While 'Adds a new reservation' implies a write operation, the description doesn't address critical behavioral aspects: whether this requires specific permissions, if it's idempotent, what happens on conflicts (e.g., overlapping dates), error conditions, or the response format. For a mutation tool with 11 parameters and no annotations, this is a significant gap.

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 with zero wasted words. It's front-loaded with the core action ('Adds a new reservation') and avoids redundancy. Every word earns its place, making it highly concise and well-structured.

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 (11 parameters, mutation operation, no output schema, and no annotations), the description is inadequate. It doesn't explain the tool's behavior, error handling, or return values, leaving the agent to guess. For a reservation creation tool in a system with many sibling tools, more context is needed to ensure correct usage.

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 description coverage is 100%, with all 11 parameters documented in the input schema. The description adds minimal value beyond the schema by vaguely referring to 'specified details' without explaining parameter relationships or business logic (e.g., how CustomerId relates to ServiceId). This meets the baseline of 3 since the schema does the heavy lifting.

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 a new reservation') and specifies the scope ('with the specified details'), which is a specific verb+resource combination. However, it doesn't explicitly distinguish this tool from sibling tools like 'updateReservations' or 'cancelReservations', which would require mentioning it's specifically for creation rather than modification or cancellation.

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. There's no mention of prerequisites (e.g., existing customer/service), exclusions (e.g., not for modifying existing reservations), or explicit alternatives like 'updateReservations' for changes. The agent must infer usage from the tool name alone.

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