Skip to main content
Glama
mehmetfiskindal

Cursor Pro Limits MCP Server

update_usage

Manually update usage statistics for Cursor Pro's AI service quotas, including Sonnet 4.5, Gemini, and GPT-5 request counts, to maintain accurate tracking of subscription limits.

Instructions

Update usage statistics (for testing or manual updates)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sonnet45RequestsNoNumber of Sonnet 4.5 requests
geminiRequestsNoNumber of Gemini requests
gpt5RequestsNoNumber of GPT-5 requests
totalRequestsNoTotal number of requests

Implementation Reference

  • The main handler function for the 'update_usage' tool. It processes optional input arguments, constructs partial updates, calls the monitor's updateLimits method to persist changes, and returns a success response.
    private async handleUpdateUsage(args: {
      sonnet45Requests?: number;
      geminiRequests?: number;
      gpt5Requests?: number;
      totalRequests?: number;
    }) {
      const updates: Partial<{
        sonnet45Requests: number;
        geminiRequests: number;
        gpt5Requests: number;
        totalRequests: number;
      }> = {};
    
      if (args.sonnet45Requests !== undefined) {
        updates.sonnet45Requests = args.sonnet45Requests;
      }
      if (args.geminiRequests !== undefined) {
        updates.geminiRequests = args.geminiRequests;
      }
      if (args.gpt5Requests !== undefined) {
        updates.gpt5Requests = args.gpt5Requests;
      }
      if (args.totalRequests !== undefined) {
        updates.totalRequests = args.totalRequests;
      }
    
      this.monitor.updateLimits(updates);
    
      return {
        content: [
          {
            type: 'text',
            text: `✅ Usage statistics updated successfully.`,
          },
        ],
      };
    }
  • Input schema definition for the 'update_usage' tool, specifying optional numeric parameters for updating different service request counts.
      name: 'update_usage',
      description:
        'Update usage statistics (for testing or manual updates)',
      inputSchema: {
        type: 'object',
        properties: {
          sonnet45Requests: {
            type: 'number',
            description: 'Number of Sonnet 4.5 requests',
          },
          geminiRequests: {
            type: 'number',
            description: 'Number of Gemini requests',
          },
          gpt5Requests: {
            type: 'number',
            description: 'Number of GPT-5 requests',
          },
          totalRequests: {
            type: 'number',
            description: 'Total number of requests',
          },
        },
      },
    },
  • src/index.ts:141-149 (registration)
    Tool registration in the switch statement handling CallToolRequestSchema, dispatching to the handleUpdateUsage method.
    case 'update_usage':
      return await this.handleUpdateUsage(
        args as {
          sonnet45Requests?: number;
          geminiRequests?: number;
          gpt5Requests?: number;
          totalRequests?: number;
        }
      );
  • Supporting method in CursorLimitsMonitor class that applies partial limit updates by merging with existing limits, updates the timestamp, and notifies registered callbacks.
    public updateLimits(newLimits: Partial<CursorProLimits>): void {
      this.limits = {
        ...this.limits,
        ...newLimits,
        lastUpdated: new Date(),
      };
    
      this.notifyCallbacks();
    }
Behavior2/5

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

With no annotations, the description carries full burden but lacks critical behavioral details. 'Update' implies mutation, but it doesn't disclose permissions needed, whether changes are reversible, rate limits, or what the response looks like. The testing/manual context hints at caution but is insufficient for a mutation tool.

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—every word contributes to purpose and context. It's appropriately sized and front-loaded with the core action.

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?

For a mutation tool with no annotations and no output schema, the description is incomplete. It lacks details on behavioral traits, response format, and error handling, leaving significant gaps for an agent to use it safely and effectively.

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 parameters are fully documented in the schema. The description adds no parameter-specific information beyond the general purpose, meeting the baseline for high schema coverage without adding extra value.

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 action ('Update') and resource ('usage statistics'), and specifies the context ('for testing or manual updates'). It distinguishes from sibling tools like 'get_usage_stats' (read) and 'set_subscription_tier' (different resource). However, it doesn't explicitly contrast with all siblings like 'check_alerts'.

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 context ('for testing or manual updates'), suggesting this is not for routine operations. However, it doesn't provide explicit when-to-use rules, alternatives (e.g., vs. 'set_subscription_tier'), or prerequisites, 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/mehmetfiskindal/cursor-pro-limits-mcp'

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