Skip to main content
Glama
code-rabi

Mews MCP

by code-rabi

getAllAddresses

Retrieve all address data for specified accounts in the Mews hospitality platform to manage customer information and support operations.

Instructions

Get all addresses associated with specified accounts

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
AccountIdsYesArray of account IDs to get addresses for

Implementation Reference

  • The main handler function that executes the tool logic: calls the Mews API endpoint '/api/connector/v1/addresses/getAll' with provided AccountIds and returns the result as formatted JSON.
    async execute(config: MewsAuthConfig, args: unknown): Promise<ToolResult> {
      const result = await mewsRequest(config, '/api/connector/v1/addresses/getAll', args);
      return {
        content: [{
          type: 'text',
          text: JSON.stringify(result, null, 2)
        }]
      };
    }
  • Input schema defining the required 'AccountIds' array parameter for the tool.
    inputSchema: {
      type: 'object',
      properties: {
        AccountIds: { 
          type: 'array', 
          items: { type: 'string' },
          description: 'Array of account IDs to get addresses for'
        }
      },
      required: ['AccountIds']
    },
  • Registers the getAllAddressesTool in the central allTools array, which is used to generate tool definitions for MCP server and populate the toolMap.
    getAllAddressesTool,
  • src/tools/index.ts:4-4 (registration)
    Imports the getAllAddressesTool for inclusion in the tools registry.
    import { getAllAddressesTool } from './accounts/getAllAddresses.js';
Behavior2/5

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

No annotations are provided, so the description carries full burden. It states a read operation ('Get'), implying non-destructive behavior, but lacks details on permissions, rate limits, pagination, or return format. For a tool with no annotation coverage, this leaves significant behavioral gaps.

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, efficient sentence with no wasted words. It's front-loaded with the core action and resource, making it easy to parse quickly.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given no annotations and no output schema, the description is minimally adequate for a simple read tool but lacks depth. It covers the basic purpose but misses behavioral context and usage guidance, which are important for a tool in a server with many similar 'getAll' operations.

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 100%, so the schema already documents the single parameter 'AccountIds' as an array of account IDs. The description adds minimal value by mentioning 'specified accounts', which aligns with but doesn't expand beyond the schema. Baseline 3 is appropriate when schema does the heavy lifting.

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 ('Get') and resource ('addresses') with scope ('associated with specified accounts'), making the purpose understandable. However, it doesn't explicitly differentiate from sibling tools like 'addAddresses' or other 'getAll' tools, which would require more specific context about what makes this tool unique.

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. With many sibling tools like 'getAllCustomers' or 'getAllCompanies', there's no indication of prerequisites, when this is appropriate, or what other tools might be better for related tasks.

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