Skip to main content
Glama
mehmetfiskindal

Cursor Pro Limits MCP Server

check_alerts

Monitor Cursor Pro usage limits and API quotas for Sonnet 4.5, Gemini, and GPT-5 services to receive alerts when approaching subscription thresholds.

Instructions

Check for services approaching or exceeding limits

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Primary MCP tool handler for 'check_alerts'. Calls monitor.checkAlerts(), formats alerts into Markdown summary with status emojis and details if any, or no-alerts message.
      private async handleCheckAlerts() {
        const alerts = this.monitor.checkAlerts();
    
        if (alerts.length === 0) {
          return {
            content: [
              {
                type: 'text',
                text: '✅ No alerts - all services are within normal limits.',
              },
            ],
          };
        }
    
        const alertContent = alerts
          .map(alert => {
            const status = alert.isCritical ? '🔴 CRITICAL' : '🟡 WARNING';
            return `- **${alert.service.toUpperCase()}**: ${status} (${alert.percentage.toFixed(1)}% used)`;
          })
          .join('\n');
    
        const content = `
    # Alert Summary
    
    ${alertContent}
    
    ## Details
    ${alerts
      .map(alert =>
        `
    ### ${alert.service.toUpperCase()}
    - Current: ${alert.current}/${alert.max}
    - Percentage: ${alert.percentage.toFixed(1)}%
    - Remaining: ${alert.remaining}
    - Status: ${alert.isCritical ? 'CRITICAL' : 'WARNING'}
        `.trim()
      )
      .join('\n')}
        `.trim();
    
        return {
          content: [
            {
              type: 'text',
              text: content,
            },
          ],
        };
      }
  • src/index.ts:63-70 (registration)
    Tool registration in ListTools response: defines name 'check_alerts', description, and empty input schema (no parameters required).
    {
      name: 'check_alerts',
      description: 'Check for services approaching or exceeding limits',
      inputSchema: {
        type: 'object',
        properties: {},
      },
    },
  • Helper method in CursorLimitsMonitor that checks all services for warning (>=80%) or critical (>=95%) usage and returns array of ServiceUsage for alerting services.
    public checkAlerts(): ServiceUsage[] {
      const services: Array<'sonnet45' | 'gemini' | 'gpt5' | 'total'> = [
        'sonnet45',
        'gemini',
        'gpt5',
        'total',
      ];
    
      return services
        .map(service => this.getServiceUsage(service))
        .filter(usage => usage.isWarning || usage.isCritical);
    }
  • TypeScript interface defining ServiceUsage structure used for alert outputs, including flags for warning and critical thresholds.
    export interface ServiceUsage {
      service: ServiceType;
      current: number;
      max: number;
      percentage: number;
      remaining: number;
      isWarning: boolean;
      isCritical: boolean;
    }
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 states the action ('Check') but doesn't describe what 'approaching or exceeding limits' means operationally, whether this is a read-only operation, what permissions are needed, or how results are returned. This leaves significant gaps for a tool that likely interacts with system limits.

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 purpose without any wasted words. It is appropriately sized for a zero-parameter tool and front-loaded with the essential information.

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

Completeness3/5

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

For a zero-parameter tool with no output schema, the description is minimally adequate but lacks detail on what 'check' entails (e.g., returns alerts, thresholds, or just status). Given the sibling tools suggest a usage/limits context, more specificity about behavioral aspects would improve completeness.

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 tool has 0 parameters with 100% schema description coverage, so the schema fully documents the absence of inputs. The description appropriately doesn't add parameter details, maintaining focus on the tool's purpose without redundancy. Baseline 4 is correct for zero-parameter tools.

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 tool's purpose with a specific verb ('Check') and resource ('services approaching or exceeding limits'), making it immediately understandable. It doesn't explicitly distinguish from siblings like 'get_service_usage' or 'get_usage_stats', but the focus on 'limits' provides some differentiation.

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 like 'get_service_usage' or 'get_usage_stats'. The description implies usage for monitoring limit thresholds but doesn't specify prerequisites, frequency, or exclusions.

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/mehmetfiskindal/cursor-pro-limits-mcp'

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