Skip to main content
Glama
code-rabi

Mews MCP

by code-rabi

deleteCompanies

Remove specified companies from the Mews hospitality platform by providing their IDs to manage customer and company data effectively.

Instructions

Deletes specified companies

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
CompanyIdsYesArray of company IDs to delete

Implementation Reference

  • The execute method implementing the core logic of the deleteCompanies tool. It processes input arguments and sends a request to the Mews API endpoint for deleting companies.
    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/delete', requestData);
      return {
        content: [{
          type: 'text',
          text: JSON.stringify(result, null, 2)
        }]
      };
    }
  • Input schema defining the expected parameters for the deleteCompanies tool: an object with a required 'CompanyIds' array of strings (max 1000 items).
    inputSchema: {
      type: 'object',
      properties: {
        CompanyIds: {
          type: 'array',
          items: { type: 'string' },
          description: 'Array of company IDs to delete',
          maxItems: 1000
        }
      },
      required: ['CompanyIds'],
      additionalProperties: false
    },
  • Registers the deleteCompaniesTool by including it in the allTools array, which is used for tool lookup (toolMap) and MCP server definitions (getToolDefinitions).
    deleteCompaniesTool,
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 only states the action ('deletes') without disclosing critical behavioral traits. It doesn't mention whether deletion is permanent/reversible, requires specific permissions, has side effects on related data, or provides confirmation/error responses. For a destructive operation, 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?

Extremely concise with just three words, front-loaded with the core action. Every word earns its place by specifying the operation and target, though this brevity contributes to gaps in other dimensions.

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 tool with no annotations and no output schema, the description is incomplete. It doesn't address behavioral risks, return values, error conditions, or usage context. Given the complexity of deletion operations and lack of structured safety hints, more guidance is needed.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100% with the parameter CompanyIds fully documented in the schema. The description doesn't add parameter details beyond implying deletion targets, but with zero parameters needing semantic clarification, a baseline of 4 is appropriate as the schema handles all parameter documentation.

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 'Deletes specified companies' clearly states the verb (deletes) and resource (companies), but it's vague about scope and doesn't distinguish from sibling tools like deleteCustomers or deleteLoyaltyMemberships. It specifies 'companies' but doesn't clarify if this means all company data or just specific records.

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 on when to use this tool versus alternatives like updateCompanies or getAllCompanies. The description doesn't mention prerequisites, consequences, or appropriate contexts for deletion versus other operations on companies.

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