Skip to main content
Glama
code-rabi

Mews MCP

by code-rabi

addCustomer

Create a new customer profile in the Mews hospitality platform by entering personal details, contact information, and demographic data.

Instructions

Create a new customer

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
FirstNameNoCustomer first name
LastNameNoCustomer last name
EmailNoCustomer email address
PhoneNoCustomer phone number
BirthDateNoBirth date (ISO 8601 format)
BirthPlaceNoPlace of birth
CitizenshipCountryCodeNoISO country code of citizenship
GenderCodeNoGender code
LanguageCodeNoPreferred language ISO code
NationalityCountryCodeNoISO country code of nationality
OccupationNoCustomer occupation
TitleNoCustomer title (Mr, Ms, etc.)
SecondLastNameNoSecond last name
TaxIdentifierNoTax identification number
LoyaltyCodeNoLoyalty program code

Implementation Reference

  • The execute handler function for the 'addCustomer' tool. It calls the Mews API endpoint '/api/connector/v1/customers/add' with the provided arguments and returns the JSON-formatted result.
    async execute(config: MewsAuthConfig, args: unknown): Promise<ToolResult> {
      const result = await mewsRequest(config, '/api/connector/v1/customers/add', args);
      return {
        content: [{
          type: 'text',
          text: JSON.stringify(result, null, 2)
        }]
      };
    }
  • The inputSchema object defining the expected parameters for the addCustomer tool, including customer details like names, email, phone, birth info, etc.
    inputSchema: {
      type: 'object',
      properties: {
        FirstName: { type: 'string', description: 'Customer first name' },
        LastName: { type: 'string', description: 'Customer last name' },
        Email: { type: 'string', format: 'email', description: 'Customer email address' },
        Phone: { type: 'string', description: 'Customer phone number' },
        BirthDate: { type: 'string', description: 'Birth date (ISO 8601 format)' },
        BirthPlace: { type: 'string', description: 'Place of birth' },
        CitizenshipCountryCode: { type: 'string', description: 'ISO country code of citizenship' },
        GenderCode: { type: 'string', description: 'Gender code' },
        LanguageCode: { type: 'string', description: 'Preferred language ISO code' },
        NationalityCountryCode: { type: 'string', description: 'ISO country code of nationality' },
        Occupation: { type: 'string', description: 'Customer occupation' },
        Title: { type: 'string', description: 'Customer title (Mr, Ms, etc.)' },
        SecondLastName: { type: 'string', description: 'Second last name' },
        TaxIdentifier: { type: 'string', description: 'Tax identification number' },
        LoyaltyCode: { type: 'string', description: 'Loyalty program code' }
      }
    },
  • Registration of the addCustomerTool in the allTools array alongside other customer tools.
    getAllCustomersTool,
    addCustomerTool,
    updateCustomersTool,
    deleteCustomersTool,
    mergeCustomersTool,
  • src/tools/index.ts:9-9 (registration)
    Import statement that brings the addCustomerTool into the index for registration.
    import { addCustomerTool } from './customers/addCustomer.js';
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. 'Create a new customer' implies a write operation but doesn't specify permissions required, whether this is idempotent, what happens on duplicate entries, or what the response contains. For a mutation tool with 15 parameters and no annotation coverage, this is insufficient behavioral context.

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 extremely concise - a single three-word phrase that communicates the core purpose efficiently. There's zero wasted language, and the information is front-loaded with no unnecessary elaboration.

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 mutation tool with 15 parameters, no annotations, and no output schema, the description is inadequate. It doesn't explain what happens after creation, what validation occurs, what errors might be returned, or how this tool relates to other customer management operations like 'updateCustomers' or 'deleteCustomers'.

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%, with all 15 parameters well-documented in the schema itself. The description adds no parameter information beyond what's already in the schema. According to guidelines, when schema coverage is high (>80%), the baseline is 3 even with no param info in the description.

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 verb ('Create') and resource ('a new customer'), making the purpose immediately understandable. However, it doesn't differentiate from sibling tools like 'addCompany' or 'addLoyaltyMemberships' which follow similar patterns, so it doesn't reach the highest 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. There's no mention of prerequisites, when to choose this over similar tools like 'addCompany', or any contextual constraints. It simply states what the tool does without usage context.

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