Skip to main content
Glama
code-rabi

Mews MCP

by code-rabi

addAccountingItems

Add charges, payments, and other financial items to customer bills in the Mews hospitality platform to manage billing and accounting transactions.

Instructions

Adds new accounting items (charges, payments, etc.) to customer bills

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
AccountingItemsYesArray of accounting item objects to create

Implementation Reference

  • The main handler function that executes the tool by calling the Mews API endpoint /api/connector/v1/accountingItems/add with the provided accounting items data.
    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/accountingItems/add', requestData);
      return {
        content: [{
          type: 'text',
          text: JSON.stringify(result, null, 2)
        }]
      };
    }
  • The input schema defining the structure of the AccountingItems array, including required fields like CustomerId, AccountingCategoryId, and Amount object.
    inputSchema: {
      type: 'object',
      properties: {
        AccountingItems: {
          type: 'array',
          items: {
            type: 'object',
            properties: {
              CustomerId: { type: 'string', description: 'Customer ID' },
              AccountingCategoryId: { type: 'string', description: 'Accounting category ID' },
              Amount: {
                type: 'object',
                properties: {
                  Currency: { type: 'string', description: 'Currency code' },
                  Value: { type: 'number', description: 'Amount value' }
                },
                required: ['Currency', 'Value'],
                description: 'Amount object'
              },
              ConsumedUtc: { type: 'string', description: 'Consumption date/time (ISO 8601)' },
              Notes: { type: 'string', description: 'Item notes' },
              Name: { type: 'string', description: 'Item name' }
            },
            required: ['CustomerId', 'AccountingCategoryId', 'Amount']
          },
          description: 'Array of accounting item objects to create'
        }
      },
      required: ['AccountingItems'],
      additionalProperties: false
    },
  • Registration of the addAccountingItemsTool in the allTools array, making it available for execution.
    addAccountingItemsTool,
  • Import statement that brings the addAccountingItemsTool into the index file for registration.
    import { addAccountingItemsTool } from './finance/addAccountingItems.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 it 'Adds new accounting items', implying a write/mutation operation, but doesn't disclose behavioral traits like required permissions, whether it's idempotent, error handling, or side effects (e.g., bill recalculation). For a mutation tool with zero annotation coverage, this is inadequate.

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?

Single sentence, front-loaded with the core action, zero waste. Efficiently conveys purpose without redundancy.

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 insufficient. It lacks critical context: what happens after adding items (e.g., bill update, notifications), error conditions, or response format. Siblings include related tools like 'addPayment', but no guidance on differentiation.

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%, with all parameters documented in the schema. The description adds minimal value beyond the schema, only implying that items are added to 'customer bills' (context not in schema). It doesn't explain parameter interactions or provide examples, so baseline 3 is appropriate.

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') and resource ('accounting items to customer bills'), with examples of item types ('charges, payments, etc.'). It distinguishes from siblings like 'addPayment' by specifying it's for accounting items on bills, not standalone payments. However, it doesn't explicitly contrast with 'exportAccountingItems' or 'getAllAccountingItems'.

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 explicit guidance on when to use this tool versus alternatives like 'addPayment' or 'chargeCreditCard'. The description implies it's for adding accounting items to bills, but doesn't specify prerequisites (e.g., existing customer/bill) or exclusions (e.g., not for updating existing items).

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