Skip to main content
Glama
code-rabi

Mews MCP

by code-rabi

getAllLoyaltyPrograms

Retrieve all loyalty programs from the Mews hospitality platform. Filter results by identifiers, names, activity states, or creation/update dates to manage customer rewards programs.

Instructions

Returns all loyalty programs of the enterprise, optionally filtered by specific loyalty program identifiers or other filter parameters.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
ChainIdsNoUnique identifiers of the chain. If not specified, the operation returns data for all chains within scope of the Access Token.
CreatedUtcNoThe time interval during which the program was created (max length 3 months)
UpdatedUtcNoThe time interval during which the program was last updated (max length 3 months)
LoyaltyProgramIdsNoUnique identifiers of Loyalty programs.
ActivityStatesNoWhether to return only active, only deleted or both records.
NamesNoNames of the loyalty programs.
LimitationNoLimitation on the quantity of data returned

Implementation Reference

  • Handler function that executes the tool: defaults Limitation.Count to 100, spreads input args, calls mewsRequest to GET loyalty programs, returns JSON stringified result.
    async execute(config: MewsAuthConfig, args: unknown): Promise<ToolResult> {
      const inputArgs = args as Record<string, unknown>;
      
      // Ensure required parameters have defaults
      const requestData: Record<string, unknown> = {
        Limitation: {
          Count: 100
        },
        ...inputArgs
      };
    
      const result = await mewsRequest(config, '/api/connector/v1/loyaltyPrograms/getAll', requestData);
      return {
        content: [{
          type: 'text',
          text: JSON.stringify(result, null, 2)
        }]
      };
    }
  • Input schema defining parameters for filtering and paginating loyalty programs query.
    inputSchema: {
      type: 'object',
      properties: {
        ChainIds: {
          type: 'array',
          items: { type: 'string' },
          description: 'Unique identifiers of the chain. If not specified, the operation returns data for all chains within scope of the Access Token.',
          maxItems: 1000
        },
        CreatedUtc: {
          type: 'object',
          properties: {
            StartUtc: { type: 'string', description: 'Start of creation date range (ISO 8601)' },
            EndUtc: { type: 'string', description: 'End of creation date range (ISO 8601)' }
          },
          description: 'The time interval during which the program was created (max length 3 months)'
        },
        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: 'The time interval during which the program was last updated (max length 3 months)'
        },
        LoyaltyProgramIds: {
          type: 'array',
          items: { type: 'string' },
          description: 'Unique identifiers of Loyalty programs.',
          maxItems: 1000
        },
        ActivityStates: {
          type: 'array',
          items: { type: 'string' },
          description: 'Whether to return only active, only deleted or both records.'
        },
        Names: {
          type: 'array',
          items: { type: 'string' },
          description: 'Names of the loyalty programs.',
          maxItems: 1000
        },
        Limitation: {
          type: 'object',
          properties: {
            Count: { type: 'number', description: 'Maximum number of loyalty programs to return' },
            Cursor: { type: 'string', description: 'Pagination cursor for next page' }
          },
          description: 'Limitation on the quantity of data returned'
        }
      },
      additionalProperties: false
    },
  • Import statement bringing the tool into the index for registration.
    import { getAllLoyaltyProgramsTool } from './loyalty/getAllLoyaltyPrograms.js';
  • Tool added to the allTools array, which is used to populate toolMap and getToolDefinitions for MCP server registration.
    getAllLoyaltyProgramsTool,
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 mentions filtering and optional parameters but fails to describe key behaviors such as pagination (implied by 'Limitation' in schema but not explained), rate limits, authentication requirements, or error handling. This leaves significant gaps for an agent to understand operational constraints.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, efficient sentence that front-loads the core purpose and briefly mentions filtering. It avoids redundancy and waste, though it could be slightly more structured by explicitly listing key filter types for clarity.

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 (7 parameters, nested objects) and lack of annotations and output schema, the description is insufficient. It doesn't explain the return format, pagination behavior, or error scenarios, which are critical for a tool with multiple filter options and no structured output documentation. This leaves the agent with incomplete context for 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?

The schema description coverage is 100%, so the schema already documents all parameters thoroughly. The description adds minimal value by mentioning 'optionally filtered by specific loyalty program identifiers or other filter parameters,' which loosely maps to parameters like 'LoyaltyProgramIds' but doesn't provide additional semantics beyond what the schema offers. This meets the baseline for high schema coverage.

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 loyalty programs of the enterprise'), making the purpose specific and understandable. However, it doesn't explicitly differentiate from sibling tools like 'getAllLoyaltyTiers' or 'getAllLoyaltyMemberships', which reduces it from a perfect score.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage through 'optionally filtered by specific loyalty program identifiers or other filter parameters,' suggesting when to use it for filtered vs. unfiltered retrieval. However, it lacks explicit guidance on when to choose this over other 'getAll' tools or alternatives like 'export' tools, leaving some ambiguity.

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