Skip to main content
Glama
JaxonDigital

Optimizely DXP MCP Server

by JaxonDigital

get_rate_limit_status

Check current Optimizely DXP API rate limits to monitor remaining requests, reset times, and usage percentages before executing batch operations.

Instructions

⏳ View current API rate limit status. REAL-TIME: <1s. Shows requests remaining (per minute and hourly), reset times, and current usage percentage. Optimizely API limits: 30/min, 500/hour per project. Use before batch operations to avoid hitting limits. Optional: project. Returns rate limit metrics and reset timestamps.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
projectNameNo
projectIdNo

Implementation Reference

  • Tool availability configuration defining get_rate_limit_status as available across all hosting types in the Monitoring category with description 'Get rate limit status'.
    'get_rate_limit_status': {
        hostingTypes: ['dxp-paas', 'dxp-saas', 'self-hosted', 'unknown'],
        category: 'Monitoring',
        description: 'Get rate limit status'
    },
  • Lists 'get_rate_limit_status' in noCacheOperations set, ensuring real-time results without caching.
        'get_monitoring_stats',
        'get_rate_limit_status',
        ...(Array.isArray(options.noCacheOperations)
            ? options.noCacheOperations
            : options.noCacheOperations || [])
    ]),
  • Implements getStatus(projectId) method returning comprehensive RateLimitStatus object with current usage, limits, throttling, backoff, and failure counts. This is the core execution logic for the get_rate_limit_status tool.
    getStatus(projectId: string): RateLimitStatus {
        const now = Date.now();
        const limits = this.projectLimits.get(projectId);
        const throttle = this.throttleState.get(projectId);
    
        if (!limits) {
            return {
                projectId,
                requestsLastMinute: 0,
                requestsLastHour: 0,
                isThrottled: false,
                consecutiveFailures: 0,
                backoffUntil: null,
                lastRequest: 0
            };
        }
    
        const oneMinuteAgo = now - (60 * 1000);
        const oneHourAgo = now - (60 * 60 * 1000);
    
        return {
            projectId,
            requestsLastMinute: limits.requests.filter(r => r.timestamp > oneMinuteAgo).length,
            requestsLastHour: limits.requests.filter(r => r.timestamp > oneHourAgo).length,
            maxRequestsPerMinute: this.options.maxRequestsPerMinute,
            maxRequestsPerHour: this.options.maxRequestsPerHour,
            isThrottled: throttle ? throttle.retryAfter > now : false,
            throttleRetryAfter: throttle?.retryAfter,
            consecutiveFailures: limits.consecutiveFailures,
            backoffUntil: limits.backoffUntil > now ? limits.backoffUntil : null,
            lastRequest: limits.lastRequest
        };
    }
Behavior4/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 effectively describes key traits: real-time performance (<1s), what information is shown (requests remaining, reset times, usage percentage), and API limits (30/min, 500/hour per project). It doesn't cover error handling or authentication needs, but provides substantial operational context.

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 efficiently structured with key information front-loaded: purpose, performance, data shown, limits, usage guidance, parameters, and returns. Every sentence adds value without redundancy, making it easy to parse quickly.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a read-only tool with no output schema, the description provides comprehensive context about what metrics are returned (rate limit metrics and reset timestamps) and operational details. It covers purpose, behavior, and usage well, though parameter semantics could be more complete given the 0% schema coverage.

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 has 0% description coverage for its 2 parameters (projectName, projectId), and the description only mentions 'Optional: project' without explaining the difference between name and ID or when to use each. This adds minimal value beyond the schema, resulting in a baseline score for inadequate parameter documentation.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's purpose with specific verbs ('View current API rate limit status') and resource ('Optimizely API'). It distinguishes from siblings by focusing on rate limits rather than logs, deployments, or other operations, making its scope immediately apparent.

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

Usage Guidelines5/5

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

The description explicitly states when to use this tool ('Use before batch operations to avoid hitting limits'), providing clear context for its application. It implies alternatives by focusing on rate limit checks, though no specific sibling tools are named for comparison.

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/JaxonDigital/optimizely-dxp-mcp'

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