Skip to main content
Glama
code-rabi

Mews MCP

by code-rabi

getAllTaxations

Retrieve all supported taxations from Mews hospitality platform to manage tax environments and configure financial settings.

Instructions

Returns all taxations supported in tax environments

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
TaxEnvironmentIdsNoFilter by tax environment IDs

Implementation Reference

  • The execute function implementing the getAllTaxations tool logic, which parses input arguments and makes an HTTP request to the '/api/connector/v1/taxations/getAll' endpoint using mewsRequest utility.
    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/taxations/getAll', requestData);
      return {
        content: [{
          type: 'text',
          text: JSON.stringify(result, null, 2)
        }]
      };
    }
  • Input schema definition for the getAllTaxations tool, specifying an optional array of TaxEnvironmentIds.
    inputSchema: {
      type: 'object',
      properties: {
        TaxEnvironmentIds: {
          type: 'array',
          items: { type: 'string' },
          description: 'Filter by tax environment IDs'
        }
      },
      additionalProperties: false
    },
  • Registration of getAllTaxationsTool in the allTools array, making it available for execution.
    getAllTaxationsTool,
  • Import statement for getAllTaxationsTool from its implementation file.
    import { getAllTaxationsTool } from './configuration/getAllTaxations.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 for behavioral disclosure. While 'Returns' implies a read-only operation, it doesn't specify whether this is a complete list or filtered view, whether there are pagination considerations, rate limits, authentication requirements, or what format the taxations are returned in. For a tool with zero annotation coverage, this leaves significant behavioral questions unanswered.

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 that states the core functionality without unnecessary words. It's appropriately sized for a simple retrieval tool and front-loads the essential information about what the tool does.

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?

For a simple retrieval tool with good schema coverage but no annotations or output schema, the description provides the basic purpose but lacks important context. It doesn't explain what 'taxations' includes (types, formats, structure), doesn't mention whether filtering is optional or required, and provides no information about the return format or potential limitations.

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 schema has 100% description coverage, with the single parameter clearly documented as 'Filter by tax environment IDs.' The description doesn't add any meaningful parameter semantics beyond what the schema already provides, so it earns the baseline score of 3 for adequate but not additive parameter documentation.

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 ('Returns') and resource ('all taxations supported in tax environments'), making the purpose immediately understandable. However, it doesn't distinguish this tool from similar 'getAll' siblings like getAllTaxEnvironments, which would require explicit differentiation for a perfect score.

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 siblings like getAllTaxEnvironments that might return related data, there's no indication of when this specific taxation retrieval tool is appropriate or what distinguishes it from other data retrieval tools in the system.

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