Skip to main content
Glama
code-rabi

Mews MCP

by code-rabi
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Remote

getAllLanguages

Retrieve all supported languages from the Mews hospitality platform API to configure multilingual settings for customer and company management.

Instructions

Returns all languages supported by the API

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • src/tools/configuration/getAllLanguages.ts:14-22 (handler)
    Handler function that executes the getAllLanguages tool by calling the Mews API endpoint '/api/connector/v1/languages/getAll' and returning the result as JSON.
    async execute(config: MewsAuthConfig, args: unknown): Promise<ToolResult> {
  const result = await mewsRequest(config, '/api/connector/v1/languages/getAll', {});
  return {
    content: [{
      type: 'text',
      text: JSON.stringify(result, null, 2)
    }]
  };
}
  • src/tools/configuration/getAllLanguages.ts:8-12 (schema)
    Input schema defining no parameters for the getAllLanguages tool.
    inputSchema: {
  type: 'object',
  properties: {},
  additionalProperties: false
},
  • src/tools/index.ts:117-117 (registration)
    Registration of the getAllLanguagesTool in the central allTools array.
    getAllLanguagesTool,

Tool Definition Quality

B3.2/5.0
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 fails to mention potential behaviors like pagination, rate limits, authentication needs, or error handling. For a tool with zero annotation coverage, this leaves significant gaps in understanding how it operates.

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, clear sentence that efficiently conveys the core functionality without any wasted words. It is front-loaded with the essential information, making it highly concise and well-structured for quick comprehension.

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, no annotations), the description is minimally adequate. It explains what the tool does but lacks details on return format, error conditions, or integration context. For a basic read operation, it meets the minimum viable standard but could be more informative to fully guide an 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 the input schema has 100% description coverage (though empty). The description does not need to add parameter semantics, as there are none to document. A baseline score of 4 is appropriate since the description accurately reflects the lack of inputs without unnecessary elaboration.

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 languages supported by the API'), making the purpose specific and understandable. However, it does not explicitly differentiate from sibling tools like 'getLanguageTexts' or other 'getAll' tools, which slightly limits its clarity in a crowded namespace.

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, such as 'getLanguageTexts' or other data retrieval tools in the sibling list. It lacks context on prerequisites, exclusions, or specific use cases, leaving the agent to infer usage based on the 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