Skip to main content
Glama

rezdy_agent_configure

Configure Rezdy Agent API access with your API key and environment to enable travel product search, booking, and payment processing.

Instructions

Configure Rezdy Agent API connection with API key and environment

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
apiKeyYesRezdy Agent API key
environmentNoAPI environment (production or staging)production

Implementation Reference

  • The handleConfigure function executes the rezdy_agent_configure tool logic. It merges args with environment variables, validates the config using RezdyAgentConfigSchema, instantiates the RezdyAgentClient, and returns a success message.
    private async handleConfigure(args: any) {
      // Allow configuration from environment variables if not provided in args
      const configData = {
        apiKey: args.apiKey || process.env.REZDY_API_KEY,
        environment: args.environment || process.env.REZDY_ENVIRONMENT || 'production',
        baseUrl: process.env.REZDY_BASE_URL,
        stagingUrl: process.env.REZDY_STAGING_URL,
      };
    
      // Remove undefined values
      Object.keys(configData).forEach(key => {
        if (configData[key as keyof typeof configData] === undefined) {
          delete configData[key as keyof typeof configData];
        }
      });
    
      const config = RezdyAgentConfigSchema.parse(configData);
      this.rezdyClient = new RezdyAgentClient(config);
      
      return {
        content: [
          {
            type: 'text',
            text: `Rezdy Agent API configured successfully for ${config.environment} environment`,
          },
        ],
      };
    }
  • RezdyAgentConfigSchema Zod validation schema that defines and validates the configuration input: apiKey (required string), baseUrl/stagingUrl (with defaults), and environment (production/staging enum).
    export const RezdyAgentConfigSchema = z.object({
      apiKey: z.string(),
      baseUrl: z.string().default('https://api.rezdy.com/v1'),
      stagingUrl: z.string().default('https://api-staging.rezdy.com/v1'),
      environment: z.enum(['production', 'staging']).default('production'),
    });
    
    export type RezdyAgentConfig = z.infer<typeof RezdyAgentConfigSchema>;
  • src/index.ts:54-73 (registration)
    Tool registration in the ListToolsRequestSchema handler. Defines the tool name 'rezdy_agent_configure', description, and JSON input schema with apiKey (required) and environment (production/staging) properties.
    {
      name: 'rezdy_agent_configure',
      description: 'Configure Rezdy Agent API connection with API key and environment',
      inputSchema: {
        type: 'object',
        properties: {
          apiKey: {
            type: 'string',
            description: 'Rezdy Agent API key',
          },
          environment: {
            type: 'string',
            enum: ['production', 'staging'],
            description: 'API environment (production or staging)',
            default: 'production',
          },
        },
        required: ['apiKey'],
      },
    },
Behavior2/5

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

No annotations are provided, yet the description fails to disclose behavioral traits: it does not state whether this validates the API key, persists credentials for subsequent calls, is idempotent, or what error conditions to expect. The phrase 'Configure... connection' implies statefulness without explaining the state management contract.

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?

Single sentence of nine words with no redundancy. While appropriately sized, it is information-poor; the conciseness reflects under-specification rather than efficient delivery of necessary context.

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?

Lacking both output schema and annotations, the description omits critical context for a configuration tool: return value structure, success/failure indicators, and side effects on subsequent tool invocations. It does not fulfill the descriptive burden for an initialization operation with no output schema.

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?

Input schema has 100% description coverage ('Rezdy Agent API key', 'API environment'). The description merely echoes these concepts ('with API key and environment') without adding semantic context—such as where to obtain the key, that environment defaults to production, or that staging is for testing. Baseline 3 is appropriate when schema carries the full load.

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?

States a specific verb ('Configure') and resource ('Rezdy Agent API connection'), clearly distinguishing from operational siblings like 'create_booking' or 'get_product'. However, 'connection' is slightly abstract—it could specify whether this establishes authentication credentials or initializes a client session.

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?

Provides no guidance on when to invoke this tool versus alternatives, nor does it state that this is likely a prerequisite that must be called before other rezdy_agent_* operations. For a configuration/initialization tool, explicit sequencing guidance is critical but absent.

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/jezweb/rezdy-agent-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server