Skip to main content
Glama
code-rabi

Mews MCP

by code-rabi

getAllServices

Retrieve all available services from the Mews hospitality platform, with options to filter by ID, type, or update date range for inventory management.

Instructions

Returns all services offered by the enterprise

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
ServiceIdsNoFilter by specific service IDs
ServiceTypesNoFilter by service types
UpdatedUtcNoDate range filter for service updates

Implementation Reference

  • The execute handler function that processes input arguments, calls the Mews API endpoint '/api/connector/v1/services/getAll', and returns the JSON-formatted 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/services/getAll', requestData);
      return {
        content: [{
          type: 'text',
          text: JSON.stringify(result, null, 2)
        }]
      };
    }
  • Defines the input schema for the tool, including optional filters for ServiceIds (array of strings, max 1000), ServiceTypes (array of strings), and UpdatedUtc date range.
    inputSchema: {
      type: 'object',
      properties: {
        ServiceIds: {
          type: 'array',
          items: { type: 'string' },
          description: 'Filter by specific service IDs',
          maxItems: 1000
        },
        ServiceTypes: {
          type: 'array',
          items: { type: 'string' },
          description: 'Filter by service types'
        },
        UpdatedUtc: {
          type: 'object',
          properties: {
            StartUtc: { type: 'string', description: 'Start of update date range (ISO 8601)' },
            EndUtc: { type: 'string', description: 'End of update date range (ISO 8601)' }
          },
          description: 'Date range filter for service updates'
        }
      },
      additionalProperties: false
    },
  • Registers getAllServicesTool in the central allTools array alongside other services tools, enabling its inclusion in toolMap and getToolDefinitions().
    // Services tools
    getAllServicesTool,
    getAllSpacesTool,
    getAllSpaceCategoriesTool,
  • Imports the getAllServicesTool from its implementation file for use in the tools registry.
    import { getAllServicesTool } from './services/getAllServices.js';
Behavior2/5

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

With no annotations provided, the description carries full burden but only states it 'returns all services,' lacking details on permissions, rate limits, pagination, or data freshness. It doesn't disclose behavioral traits like whether it's read-only, safe, or has performance implications, which is inadequate for a tool with parameters.

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, front-loading the core purpose ('Returns all services') without unnecessary elaboration. It's appropriately sized for a straightforward tool.

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. It doesn't explain return values, error handling, or behavioral context, which is insufficient for a tool with filtering parameters and potential complexity in enterprise services.

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 fully documents the three parameters (ServiceIds, ServiceTypes, UpdatedUtc). The description adds no additional meaning beyond implying a retrieval operation, resulting in a baseline score of 3 as the schema handles parameter semantics 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 verb ('Returns') and resource ('all services offered by the enterprise'), making the purpose immediately understandable. However, it doesn't differentiate from sibling 'getAll' tools (like getAllCompanies, getAllCustomers) beyond specifying 'services' as the resource type, missing explicit distinction in scope or behavior.

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?

No guidance is provided on when to use this tool versus alternatives. The description doesn't mention any prerequisites, exclusions, or comparisons to other tools (e.g., whether it's for bulk retrieval vs. specific lookups), leaving usage context 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