Skip to main content
Glama
code-rabi

Mews MCP

by code-rabi

cancelReservations

Cancel hotel reservations in Mews by providing reservation IDs, specifying reasons, notes, and fee options.

Instructions

Cancels specified reservations

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
ReservationIdsYesArray of reservation IDs to cancel
CancellationReasonNoReason for cancellation
NotesNoCancellation notes
ChargeCancellationFeeNoWhether to charge cancellation fee

Implementation Reference

  • Executes the tool by parsing input args, sending a request to Mews API /api/connector/v1/reservations/cancel, and returning the JSON result.
    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/cancel', requestData);
      return {
        content: [{
          type: 'text',
          text: JSON.stringify(result, null, 2)
        }]
      };
    }
  • Input schema defining the parameters for canceling reservations, with ReservationIds required.
    inputSchema: {
      type: 'object',
      properties: {
        ReservationIds: {
          type: 'array',
          items: { type: 'string' },
          description: 'Array of reservation IDs to cancel',
          maxItems: 1000
        },
        CancellationReason: {
          type: 'string',
          description: 'Reason for cancellation'
        },
        Notes: {
          type: 'string',
          description: 'Cancellation notes'
        },
        ChargeCancellationFee: {
          type: 'boolean',
          description: 'Whether to charge cancellation fee'
        }
      },
      required: ['ReservationIds'],
      additionalProperties: false
    },
  • Import statement bringing the cancelReservationsTool into the central tools index.
    import { cancelReservationsTool } from './reservations/cancelReservations.js';
  • Includes the cancelReservationsTool in the allTools array for global tool registry and lookup via toolMap.
    cancelReservationsTool,
Behavior2/5

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

With no annotations provided, the description carries full burden but offers minimal behavioral context. It states the action ('cancels') but doesn't disclose whether this is reversible, what permissions are required, whether notifications are sent, what happens to associated data, or any rate limits. For a destructive operation with zero annotation coverage, this is inadequate.

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

Conciseness4/5

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

The description is extremely concise at just three words, which is appropriately sized for such a simple statement. However, it's arguably too brief given the tool's complexity, and it doesn't front-load critical information about the tool's destructive nature.

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?

For a destructive mutation tool with no annotations and no output schema, the description is incomplete. It doesn't explain what 'canceling' entails operationally, what the expected outcome is, whether there are side effects, or what happens if cancellation fails. The agent would need to guess about important behavioral aspects.

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%, so the schema already fully documents all 4 parameters. The description adds no additional meaning about parameters beyond what's in the schema. The baseline score of 3 is appropriate when the schema does all the parameter documentation work.

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

Purpose3/5

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

The description 'Cancels specified reservations' clearly states the verb ('cancels') and resource ('reservations'), but it's vague about scope and doesn't differentiate from potential alternatives. It doesn't specify whether this cancels individual reservations, bulk reservations, or what 'specified' means beyond the parameter schema.

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?

No guidance is provided on when to use this tool versus alternatives. While sibling tools include 'updateReservations' which might handle status changes, the description doesn't mention this or provide any context about prerequisites, timing, or when not to use this tool.

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