Skip to main content
Glama
code-rabi

Mews MCP

by code-rabi

getAllCurrencies

Retrieve all available currencies supported by the Mews hospitality platform API for financial transactions and configuration.

Instructions

Returns all currencies supported by the API

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The execute handler function that calls the Mews API endpoint '/api/connector/v1/currencies/getAll' via mewsRequest utility and returns the result as formatted JSON text.
    async execute(config: MewsAuthConfig, args: unknown): Promise<ToolResult> {
      const result = await mewsRequest(config, '/api/connector/v1/currencies/getAll', {});
      return {
        content: [{
          type: 'text',
          text: JSON.stringify(result, null, 2)
        }]
      };
    }
  • Input schema for the getAllCurrencies tool, defining an empty object with no properties.
    inputSchema: {
      type: 'object',
      properties: {},
      additionalProperties: false
    },
  • Registration of getAllCurrenciesTool in the central allTools array used for tool registry and lookup.
    getAllCurrenciesTool,
  • Import statement that brings the getAllCurrenciesTool into the index module for registration.
    import { getAllCurrenciesTool } from './configuration/getAllCurrencies.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 of behavioral disclosure. It states the tool returns data, implying a read-only operation, but doesn't cover important aspects like rate limits, authentication requirements, error handling, or response format. For a tool with zero annotation coverage, this leaves significant gaps in understanding its behavior.

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 directly states the tool's function without unnecessary words. It's front-loaded with the core purpose and wastes no space, making it easy for an agent to parse quickly.

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?

Given the tool's simplicity (0 parameters, no output schema), the description is adequate but minimal. It covers the basic purpose but lacks context about the return format (e.g., list structure, currency fields) and behavioral details like error cases. For a read-only tool with no annotations, more completeness would be helpful, though it's not entirely inadequate.

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 the schema description coverage is 100% (though empty). The description doesn't need to explain parameters, and it correctly implies no inputs are required. This meets expectations for a parameterless tool, earning a baseline score of 4.

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 tool's purpose with a specific verb ('Returns') and resource ('all currencies supported by the API'), making it easy to understand what the tool does. However, it doesn't distinguish this tool from its sibling 'getAll' tools (e.g., getAllCountries, getAllLanguages), which follow the same pattern but for different resources.

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 prerequisites, timing considerations, or how it differs from other currency-related tools (though none are listed in siblings). The agent must infer usage from the tool name alone.

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