Skip to main content
Glama
code-rabi

Mews MCP

by code-rabi

getAllTaxEnvironments

Retrieve all available tax environments from the Mews hospitality platform to configure tax settings for properties and transactions.

Instructions

Returns all tax environments supported by the API

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The execute function that performs the core logic: calls the Mews API for all tax environments and formats the result as JSON.
    async execute(config: MewsAuthConfig, args: unknown): Promise<ToolResult> {
      const result = await mewsRequest(config, '/api/connector/v1/taxEnvironments/getAll', {});
      return {
        content: [{
          type: 'text',
          text: JSON.stringify(result, null, 2)
        }]
      };
    }
  • Input schema defining no required parameters (empty object).
    inputSchema: {
      type: 'object',
      properties: {},
      additionalProperties: false
    },
  • Registration of getAllTaxEnvironmentsTool in the allTools array export, used for tool registry and lookup.
    // Configuration tools
    getConfigurationTool,
    getAllCountriesTool,
    getAllCurrenciesTool,
    getAllTaxEnvironmentsTool,
    getAllTaxationsTool,
    getAllLanguagesTool,
    getLanguageTextsTool,
  • Import of the tool definition for inclusion in the tools registry.
    import { getAllTaxEnvironmentsTool } from './configuration/getAllTaxEnvironments.js';
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries the full burden. It states it 'Returns all tax environments', implying a read-only operation, but doesn't disclose behavioral traits like whether it's paginated, requires authentication, has rate limits, or what the return format is. This is a significant gap for a tool with zero annotation coverage.

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 with zero waste. It's front-loaded with the core action and resource, making it easy to parse. Every word earns its place, and there's no unnecessary elaboration.

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?

Given the tool's simplicity (0 parameters, no output schema), the description is minimal but incomplete. It lacks behavioral context (e.g., return format, pagination) and usage guidelines, which are important even for simple tools. With no annotations and no output schema, it should do more to inform the agent.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool has 0 parameters, and schema description coverage is 100% (since there are no parameters to describe). The description doesn't need to add parameter semantics, so a baseline of 4 is appropriate. It implicitly confirms no inputs are required by not mentioning any.

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 tax environments supported by the API'), making the purpose understandable. It distinguishes from siblings by specifying 'tax environments' rather than other resources like companies or customers. However, it doesn't explicitly differentiate from 'getAllTaxations' (a sibling tool), which could be related, so it's not a perfect 5.

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 any context, prerequisites, or exclusions, such as whether this is for setup, reporting, or other scenarios. With many sibling tools, including 'getAllTaxations', the lack of differentiation leaves usage unclear.

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