Skip to main content
Glama
code-rabi

Mews MCP

by code-rabi

exportAccountingItems

Export accounting items like charges and payments from Mews in CSV, JSON, or Excel format for a specified date range to support financial reporting and analysis.

Instructions

Exports accounting items (charges, payments, etc.) in the specified format and period

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
StartUtcYesStart date for export (ISO 8601)
EndUtcYesEnd date for export (ISO 8601)
FormatYesExport format (CSV, JSON, etc.)
AccountingItemIdsNoSpecific accounting item IDs to export
CurrencyNoCurrency code for export amounts
TimeZoneNoTime zone for date formatting

Implementation Reference

  • The execute function implementing the core logic of the exportAccountingItems tool by forwarding input arguments to the Mews API endpoint '/api/connector/v1/exports/accountingItems' and returning the JSON-formatted result.
    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/exports/accountingItems', requestData);
      return {
        content: [{
          type: 'text',
          text: JSON.stringify(result, null, 2)
        }]
      };
    }
  • Input schema for the exportAccountingItems tool, specifying required date range and format, with optional filters for accounting items, currency, and timezone.
    inputSchema: {
      type: 'object',
      properties: {
        StartUtc: {
          type: 'string',
          description: 'Start date for export (ISO 8601)'
        },
        EndUtc: {
          type: 'string',
          description: 'End date for export (ISO 8601)'
        },
        Format: {
          type: 'string',
          description: 'Export format (CSV, JSON, etc.)',
          enum: ['Csv', 'Json', 'Excel']
        },
        AccountingItemIds: {
          type: 'array',
          items: { type: 'string' },
          description: 'Specific accounting item IDs to export',
          maxItems: 1000
        },
        Currency: {
          type: 'string',
          description: 'Currency code for export amounts'
        },
        TimeZone: {
          type: 'string',
          description: 'Time zone for date formatting'
        }
      },
      required: ['StartUtc', 'EndUtc', 'Format'],
      additionalProperties: false
    },
  • Registers the exportAccountingItemsTool in the central allTools array used for MCP server tool definitions and execution lookup.
    // Export tools
    exportAccountingItemsTool,
    exportReservationsTool,
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 mentions export functionality but lacks critical behavioral details: whether this is a read-only operation, if it generates downloadable files, has rate limits, requires specific permissions, or what the output looks like (e.g., file download vs. inline data). The description is too vague for a tool with potential side effects like file generation.

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 purpose. However, it could be more structured by separating purpose from key constraints, and it omits necessary behavioral details that would require additional sentences.

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 6-parameter export tool with no annotations and no output schema, the description is inadequate. It doesn't address what the export produces (e.g., file, data stream), error conditions, or how results are delivered. Given the complexity and lack of structured metadata, more descriptive context is needed for safe agent use.

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%, providing detailed parameter documentation. The description adds marginal value by implying date range filtering ('period') and format specification, but doesn't explain parameter interactions (e.g., if AccountingItemIds overrides date range) or provide usage examples beyond what the schema already covers.

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 ('Exports') and resource ('accounting items') with examples of what items are included ('charges, payments, etc.'). It distinguishes from sibling tools like 'getAllAccountingItems' by specifying export functionality rather than retrieval. However, it doesn't explicitly differentiate from 'exportReservations' beyond the resource type.

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 minimal guidance on when to use this tool, mentioning only the 'specified format and period' without clarifying when to choose this over 'getAllAccountingItems' for listing items or 'exportReservations' for other data exports. No alternatives, prerequisites, or exclusions are stated.

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