Skip to main content
Glama
code-rabi

Mews MCP

by code-rabi

addAddresses

Add new addresses to customer accounts in the Mews hospitality platform. Specify address details including street lines, city, postal code, and country codes for accurate account management.

Instructions

Add new addresses to accounts

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
AddressesYes

Implementation Reference

  • Handler function that executes the tool by calling the Mews API to add addresses.
    async execute(config: MewsAuthConfig, args: unknown): Promise<ToolResult> {
      const result = await mewsRequest(config, '/api/connector/v1/addresses/add', args);
      return {
        content: [{
          type: 'text',
          text: JSON.stringify(result, null, 2)
        }]
      };
    }
  • Input schema defining the structure for the Addresses array, including required AccountId and optional address fields.
    inputSchema: {
      type: 'object',
      properties: {
        Addresses: {
          type: 'array',
          items: {
            type: 'object',
            properties: {
              AccountId: { type: 'string', description: 'Account ID to add address to' },
              Line1: { type: 'string', description: 'First line of address' },
              Line2: { type: 'string', description: 'Second line of address' },
              City: { type: 'string', description: 'City' },
              PostalCode: { type: 'string', description: 'Postal/ZIP code' },
              CountryCode: { type: 'string', description: 'ISO country code' },
              CountrySubdivisionCode: { type: 'string', description: 'State/province code' }
            },
            required: ['AccountId']
          }
        }
      },
      required: ['Addresses']
    },
  • Registration of the addAddressesTool in the allTools array exported for use in the MCP server.
    getAllAddressesTool,
    addAddressesTool,
  • src/tools/index.ts:5-5 (registration)
    Import statement bringing in the addAddressesTool for registration.
    import { addAddressesTool } from './accounts/addAddresses.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 but only states the basic action ('add new addresses'). It doesn't disclose behavioral traits such as whether this is a mutation requiring permissions, if it's idempotent, what happens on duplicate addresses, error handling, or rate limits. For a write operation, this is a significant gap in transparency.

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 a single, direct sentence with no wasted words. It's front-loaded and efficiently conveys the core purpose without unnecessary elaboration, making it easy to parse quickly.

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 the complexity of a write operation with no annotations, no output schema, and 0% schema description coverage, the description is incomplete. It lacks details on behavior, error cases, return values, and how it fits with sibling tools, making it inadequate for safe and effective use by an 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?

Schema description coverage is 0%, so the description must compensate but adds no parameter information beyond the tool name. The schema fully documents the 'Addresses' array and its nested properties with descriptions, so the baseline is 3. The description doesn't enhance understanding of parameters like required fields or data formats.

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 'Add new addresses to accounts' clearly states the action (add) and target (addresses to accounts), but it's vague about scope and doesn't distinguish from sibling tools like 'getAllAddresses' or 'addCustomer'. It specifies what it does but lacks precision about how it differs from related operations.

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 like 'addCustomer' (which might include addresses) or 'getAllAddresses' (for reading). The description doesn't mention prerequisites, constraints, or typical use cases, leaving the agent without context for selection.

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