Skip to main content
Glama
code-rabi

Mews MCP

by code-rabi

addCompany

Create new company records in Mews hospitality platform by entering company details like name, tax ID, contact information, and billing email.

Instructions

Adds a new company

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
NameYesCompany name
TaxIdentifierNoTax identification number
EmailNoCompany email address
PhoneNoCompany phone number
WebsiteUrlNoCompany website URL
InvoicingEmailNoBilling email address
ContactPersonIdNoContact person customer ID

Implementation Reference

  • The async execute method implementing the core logic of the addCompany tool: parses input arguments and sends a POST request to the Mews API endpoint '/api/connector/v1/companies/add', 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/companies/add', requestData);
      return {
        content: [{
          type: 'text',
          text: JSON.stringify(result, null, 2)
        }]
      };
    }
  • Input schema for the addCompany tool, defining object properties like Name (required), TaxIdentifier, Email, Phone, WebsiteUrl, InvoicingEmail, ContactPersonId with descriptions.
    inputSchema: {
      type: 'object',
      properties: {
        Name: {
          type: 'string',
          description: 'Company name'
        },
        TaxIdentifier: {
          type: 'string',
          description: 'Tax identification number'
        },
        Email: {
          type: 'string',
          description: 'Company email address'
        },
        Phone: {
          type: 'string',
          description: 'Company phone number'
        },
        WebsiteUrl: {
          type: 'string',
          description: 'Company website URL'
        },
        InvoicingEmail: {
          type: 'string',
          description: 'Billing email address'
        },
        ContactPersonId: {
          type: 'string',
          description: 'Contact person customer ID'
        }
      },
      required: ['Name'],
      additionalProperties: false
    },
  • Import statement for the addCompanyTool from its dedicated implementation file.
    import { addCompanyTool } from './companies/addCompany.js';
  • Registration of addCompanyTool within the allTools array (alongside other company tools), used for tool discovery, definitions, and execution lookup via toolMap.
    // Company tools
    getAllCompaniesTool,
    addCompanyTool,
    updateCompaniesTool,
    deleteCompaniesTool,
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. While 'Adds' implies a write/mutation operation, the description doesn't address critical behavioral aspects: required permissions, whether the operation is idempotent, what happens on duplicate entries, error conditions, or what the response contains. For a creation tool with zero annotation coverage, this represents significant gaps in behavioral understanding.

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 maximally concise - a single three-word phrase that communicates the core purpose without any wasted words. It's appropriately sized for a simple creation operation and front-loads the essential information immediately.

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 this is a write/mutation tool with no annotations and no output schema, the description is insufficiently complete. It doesn't address what happens after creation, what identifiers are returned, error handling, or how this operation relates to the broader system context. For a company creation tool in what appears to be a CRM/reservation system, more contextual information would be helpful.

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 7 parameters well-documented in the schema itself. The description adds no parameter information beyond what's already in the structured schema. According to the scoring rules, when schema_description_coverage is high (>80%), the baseline is 3 even with no parameter information in the description, which applies here.

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 ('Adds') and resource ('a new company'), making the purpose immediately understandable. However, it doesn't differentiate this tool from similar sibling tools like 'addCustomer' or 'addAccountingItems' - it simply describes what it does without explaining how it differs from other 'add' operations in the system.

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 about when to use this tool versus alternatives. With sibling tools like 'addCustomer' and 'updateCompanies' available, there's no indication of when company creation is appropriate versus customer creation or company updates. No prerequisites, constraints, or relationship to other operations are mentioned.

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