Skip to main content
Glama
code-rabi

Mews MCP

by code-rabi

getLanguageTexts

Retrieve translated texts for specified languages and scope from the Mews hospitality platform to support multilingual operations.

Instructions

Returns translations of texts in the specified languages

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
LanguageCodesYesArray of language codes to get translations for
ScopeNoScope of texts to retrieve

Implementation Reference

  • The async execute handler function that parses arguments, calls the Mews API via mewsRequest to fetch language texts, and returns formatted JSON 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/languages/getTexts', requestData);
      return {
        content: [{
          type: 'text',
          text: JSON.stringify(result, null, 2)
        }]
      };
    }
  • Input schema specifying LanguageCodes (required array of language codes) and optional Scope for retrieving translations.
    inputSchema: {
      type: 'object',
      properties: {
        LanguageCodes: {
          type: 'array',
          items: { type: 'string' },
          description: 'Array of language codes to get translations for'
        },
        Scope: {
          type: 'string',
          description: 'Scope of texts to retrieve'
        }
      },
      required: ['LanguageCodes'],
      additionalProperties: false
    },
  • Registers getLanguageTextsTool in the central allTools array for MCP tool availability.
    getAllLanguagesTool,
    getLanguageTextsTool,
  • Imports the getLanguageTextsTool implementation to make it available for registration.
    import { getLanguageTextsTool } from './configuration/getLanguageTexts.js';
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It implies a read-only operation ('Returns'), but doesn't specify whether it requires authentication, has rate limits, what happens if languages or scopes are invalid, or the format of returned data. This leaves significant gaps for a tool with potential complexity.

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 no wasted words. It's front-loaded with the core action and resource, making it easy to parse quickly. Every part of the sentence contributes directly to understanding the tool's function.

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 no annotations and no output schema, the description is incomplete for a tool that likely returns complex translation data. It doesn't explain what 'texts' refer to (e.g., UI strings, content), how translations are structured, or error handling. For a read operation with potential nuance, more context is needed to guide effective 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%, so the schema already documents both parameters ('LanguageCodes' and 'Scope'). The description adds minimal value by mentioning 'specified languages' and 'scope of texts', which aligns with but doesn't expand beyond the schema. Baseline 3 is appropriate as the schema handles parameter documentation adequately.

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 translations') and resource ('texts in the specified languages'), making the purpose understandable. However, it doesn't differentiate from sibling tools like 'getAllLanguages' or specify what types of texts are involved, leaving some ambiguity.

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 like 'getAllLanguages' or other 'getAll' tools. It lacks context about prerequisites, such as whether texts must exist or be configured, and doesn't mention any exclusions or specific use cases.

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