Skip to main content
Glama
code-rabi

Mews MCP

by code-rabi

addAccountNotes

Add notes to customer accounts in Mews hospitality platform for tracking interactions, preferences, or important details.

Instructions

Adds new account notes to the system and assigns them to specified accounts

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
AccountNotesYesArray of note objects to create

Implementation Reference

  • The execute handler function that processes input arguments and makes an HTTP request to the Mews API endpoint '/api/connector/v1/accountNotes/add' to add account notes.
    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/accountNotes/add', requestData);
      return {
        content: [{
          type: 'text',
          text: JSON.stringify(result, null, 2)
        }]
      };
    }
  • Input schema defining the expected structure: an object with 'AccountNotes' array, each item having 'AccountId', 'Text' (required), and optional 'Type'.
    inputSchema: {
      type: 'object',
      properties: {
        AccountNotes: {
          type: 'array',
          items: {
            type: 'object',
            properties: {
              AccountId: { type: 'string', description: 'Account ID to add note to' },
              Text: { type: 'string', description: 'Note content' },
              Type: { type: 'string', description: 'Note type or category' }
            },
            required: ['AccountId', 'Text']
          },
          description: 'Array of note objects to create'
        }
      },
      required: ['AccountNotes'],
      additionalProperties: false
    },
  • Import statement bringing in the addAccountNotesTool for registration.
    import { addAccountNotesTool } from './accountNotes/addAccountNotes.js';
  • Inclusion of addAccountNotesTool in the allTools array, which is used for tool registry and lookup.
    addAccountNotesTool,
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 without disclosing behavioral traits. It doesn't mention permissions needed, whether notes are editable/deletable, rate limits, or what happens on success/failure. For a mutation tool with zero annotation coverage, 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, efficient sentence that front-loads the core action. It avoids redundancy and wastes no words, though it could be slightly more structured by separating purpose from constraints.

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 doesn't cover behavioral aspects like side effects, error handling, or return values, leaving critical gaps for agent understanding despite the clear purpose.

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 'AccountNotes' and its nested properties. The description adds no additional meaning beyond implying notes are created and assigned, matching the baseline 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 action ('Adds new account notes') and target resource ('to the system and assigns them to specified accounts'), providing a specific verb+resource combination. However, it doesn't differentiate from sibling tools like 'addTask' or 'addPayment' beyond the resource type, missing explicit sibling distinction.

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. The description lacks context about prerequisites, exclusions, or comparisons to similar tools like 'addTask' or 'updateCompanies', leaving usage entirely implicit.

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