Skip to main content
Glama
code-rabi

Mews MCP

by code-rabi

updateCompanies

Modify company details in Mews hospitality platform, including name, tax ID, contact information, and billing data for multiple companies simultaneously.

Instructions

Updates company information

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
CompanyUpdatesYesArray of company update objects

Implementation Reference

  • The handler function that executes the tool logic by making an HTTP request to the Mews API endpoint '/api/connector/v1/companies/update' with the provided input arguments.
    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/update', requestData);
      return {
        content: [{
          type: 'text',
          text: JSON.stringify(result, null, 2)
        }]
      };
    }
  • The input schema defining the structure for company updates, requiring an array of CompanyUpdates with at least CompanyId.
    inputSchema: {
      type: 'object',
      properties: {
        CompanyUpdates: {
          type: 'array',
          items: {
            type: 'object',
            properties: {
              CompanyId: { type: 'string', description: 'Unique identifier of the company to update' },
              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: ['CompanyId']
          },
          description: 'Array of company update objects'
        }
      },
      required: ['CompanyUpdates'],
      additionalProperties: false
    },
  • Import statement that brings the updateCompaniesTool into the tools index module.
    import { updateCompaniesTool } from './companies/updateCompanies.js';
  • Registration of the updateCompaniesTool in the central allTools array, making it available for the MCP server.
    updateCompaniesTool,
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 'Updates company information', implying a mutation operation, but fails to mention permissions, side effects, error handling, or response format. This is a significant gap for a mutation tool with zero annotation coverage.

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 a single, efficient sentence with no wasted words. It is front-loaded and to the point, though it could be more informative by including key details like required parameters or scope.

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 no annotations and no output schema, the description is incomplete. It lacks information on behavioral traits, error conditions, and what the tool returns, making it inadequate for safe and effective use by an AI agent.

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 detailed parameter descriptions in the input schema. The description adds no additional meaning beyond the schema, such as explaining the structure of 'CompanyUpdates' or constraints on field updates. Baseline 3 is appropriate when the schema does the heavy lifting.

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 'Updates company information' clearly states the verb ('Updates') and resource ('company information'), which is adequate. However, it lacks specificity about what fields can be updated and doesn't differentiate from sibling tools like 'updateCustomers' or 'updateReservations', making it somewhat vague.

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 is no mention of prerequisites, such as needing an existing company ID, or comparisons to tools like 'addCompany' or 'deleteCompanies', leaving the agent without contextual usage cues.

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