Skip to main content
Glama
code-rabi

Mews MCP

by code-rabi

getAllAccountNotes

Retrieve all account notes from the Mews hospitality platform with filtering options for accounts, dates, and pagination to manage customer information.

Instructions

Returns all the account notes associated with the specified accounts within the chain

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
AccountIdsNoFilter by account IDs
CreatedUtcNoDate range filter for note creation
UpdatedUtcNoDate range filter for note updates
LimitationNoPagination settings

Implementation Reference

  • The execute handler function processes input args, adds default pagination limit, calls the Mews API to retrieve account notes, and returns the JSON-formatted result.
    async execute(config: MewsAuthConfig, args: unknown): Promise<ToolResult> {
      const inputArgs = args as Record<string, unknown>;
      const requestData = {
        Limitation: {
          Count: 100
        },
        ...inputArgs
      };
    
      const result = await mewsRequest(config, '/api/connector/v1/accountNotes/getAll', requestData);
      return {
        content: [{
          type: 'text',
          text: JSON.stringify(result, null, 2)
        }]
      };
    }
  • Input schema defining filters for AccountIds, date ranges (CreatedUtc, UpdatedUtc), and pagination (Limitation).
    inputSchema: {
      type: 'object',
      properties: {
        AccountIds: {
          type: 'array',
          items: { type: 'string' },
          description: 'Filter by account IDs',
          maxItems: 1000
        },
        CreatedUtc: {
          type: 'object',
          properties: {
            StartUtc: { type: 'string', description: 'Start of creation date range (ISO 8601)' },
            EndUtc: { type: 'string', description: 'End of creation date range (ISO 8601)' }
          },
          description: 'Date range filter for note creation'
        },
        UpdatedUtc: {
          type: 'object',
          properties: {
            StartUtc: { type: 'string', description: 'Start of update date range (ISO 8601)' },
            EndUtc: { type: 'string', description: 'End of update date range (ISO 8601)' }
          },
          description: 'Date range filter for note updates'
        },
        Limitation: {
          type: 'object',
          properties: {
            Count: { type: 'number', description: 'Maximum number of notes to return' },
            Cursor: { type: 'string', description: 'Pagination cursor for next page' }
          },
          description: 'Pagination settings'
        }
      },
      additionalProperties: false
    },
  • Registration of the getAllAccountNotesTool in the central allTools array, which populates the toolMap and provides definitions for MCP server.
    // Account Notes tools
    getAllAccountNotesTool,
    addAccountNotesTool,
  • Import statement that loads the tool definition for registration in the tools index.
    import { getAllAccountNotesTool } from './accountNotes/getAllAccountNotes.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 lacks behavioral details. It doesn't disclose if this is a read-only operation, potential rate limits, authentication needs, or what 'within the chain' entails. The mention of 'Returns all' implies a retrieval, but no further context is given.

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, clear sentence that efficiently states the tool's purpose without unnecessary words. It's front-loaded with the core action, though it could be slightly more structured by explicitly mentioning filtering or scope.

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 the tool's moderate complexity (4 parameters, nested objects, no output schema) and lack of annotations, the description is minimally adequate. It covers the basic purpose but misses behavioral transparency, usage guidelines, and output details, leaving gaps for 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 input schema has 100% description coverage, so parameters are well-documented structurally. The description adds no additional semantic context beyond implying filtering by accounts, which is already covered in the schema. This meets the baseline for high schema coverage.

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 action ('Returns') and resource ('all the account notes associated with the specified accounts within the chain'), making the purpose understandable. However, it doesn't explicitly differentiate from sibling tools like 'getAllAccountingItems' or 'getAllAddresses' beyond the resource type, missing specific sibling comparison.

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. It doesn't mention prerequisites, context for 'within the chain', or compare with other note-related tools (e.g., 'addAccountNotes'), leaving the agent with no usage direction.

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