Skip to main content
Glama
code-rabi

Mews MCP

by code-rabi

getConfiguration

Retrieve enterprise and client configuration settings from the Mews hospitality platform to manage system parameters and operational preferences.

Instructions

Returns configuration of the enterprise and the client

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The tool execution handler for getConfiguration, which sends a GET request to the Mews configuration endpoint using mewsRequest utility and returns the JSON-formatted result as text content.
    async execute(config: MewsAuthConfig, args: unknown): Promise<ToolResult> {
      const result = await mewsRequest(config, '/api/connector/v1/configuration/get', {});
      return {
        content: [{
          type: 'text',
          text: JSON.stringify(result, null, 2)
        }]
      };
    }
  • Input schema for the getConfiguration tool: defines an empty object type with no properties, meaning the tool takes no input parameters.
    inputSchema: {
      type: 'object',
      properties: {},
      additionalProperties: false
    },
  • Import of the getConfigurationTool from its implementation file into the central tools index module.
    import { getConfigurationTool } from './configuration/getConfiguration.js';
  • Registration of getConfigurationTool by inclusion in the allTools array, which is used to create a toolMap for fast lookup and to generate tool definitions for MCP server registration.
    getConfigurationTool,
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 mentions returning configuration but does not disclose behavioral traits like whether it's read-only, requires authentication, includes rate limits, or what format the configuration is in. This leaves significant gaps for an agent to understand how to use it safely.

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 is front-loaded and appropriately sized for its purpose.

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 complexity of configuration data and no annotations or output schema, the description is incomplete. It does not explain what 'configuration' entails (e.g., settings, preferences, system info) or the return format, making it hard for an agent to use effectively without additional context.

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 input schema has 0 parameters with 100% coverage, so no parameter information is needed. The description does not add param details, which is acceptable here, but it could have clarified if any implicit parameters (like context) are involved. Baseline is 4 due to the lack of parameters.

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 the target ('configuration of the enterprise and the client'), making the purpose understandable. However, it does not differentiate from sibling tools like 'getAllCompanies' or 'getAllCurrencies' that also retrieve data, leaving room for ambiguity in tool selection.

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 whether it's for system-wide settings or specific client data. With many sibling 'getAll' tools, the lack of context makes it unclear when this tool is appropriate.

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