Skip to main content
Glama
PancrePal-xiaoyibao

Get笔记 MCP Server

get_rate_limit_stats

Monitor API rate limit usage for the Get笔记 MCP Server to track remaining requests and prevent service interruptions.

Instructions

获取当前API速率限制使用情况统计

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Main tool execution handler in the MCP server switch statement. Retrieves rate limit stats from the client and returns formatted JSON text content.
    case 'get_rate_limit_stats': {
      const stats = client.getRateLimitStats();
      return {
        content: [
          {
            type: 'text',
            text: JSON.stringify(stats, null, 2),
          },
        ],
      };
    }
  • src/index.ts:129-137 (registration)
    Tool registration definition including name, description, and empty input schema (no parameters required). Added to the tools array for MCP server.
      {
        name: 'get_rate_limit_stats',
        description: '获取当前API速率限制使用情况统计',
        inputSchema: {
          type: 'object',
          properties: {},
        },
      },
    ];
  • Input schema definition: empty object, indicating the tool takes no input parameters.
    inputSchema: {
      type: 'object',
      properties: {},
    },
  • GetBijiClient method that delegates rate limit stats retrieval to the internal RateLimiter instance.
    getRateLimitStats() {
      return this.rateLimiter.getStats();
    }
  • Core RateLimiter method that computes and returns current rate limiting statistics (daily count/limit, current/max QPS).
    getStats() {
      this.resetDailyCountIfNeeded();
      return {
        dailyCount: this.dailyCount,
        dailyLimit: this.dailyLimit,
        currentQPS: this.requestQueue.length,
        maxQPS: this.qps,
      };
    }
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the tool retrieves current API rate limit usage statistics, implying a read-only operation, but doesn't specify whether it requires authentication, how frequently it can be called, what format the statistics are in, or any potential side effects. This leaves significant gaps in understanding the tool's behavior.

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 in Chinese that directly states the tool's purpose without any unnecessary words or fluff. It is front-loaded and appropriately sized for a simple tool with no parameters.

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?

Given the tool's simplicity (0 parameters, no output schema, no annotations), the description is complete enough to convey the basic purpose. However, it lacks details on output format, authentication needs, or rate limits, which could be helpful for an AI agent. Without an output schema, the description doesn't explain what is returned, leaving a gap in 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 input schema has 0 parameters with 100% coverage, so no parameter documentation is needed. The description doesn't add parameter details, which is appropriate, but it could have mentioned that no inputs are required. Given the baseline for 0 parameters is 4, this score reflects that the description adequately handles the lack of parameters without redundancy.

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 '获取' (get/retrieve) and the resource 'API速率限制使用情况统计' (API rate limit usage statistics), making the purpose specific and understandable. However, it doesn't explicitly differentiate from sibling tools like knowledge_recall or knowledge_search, which are unrelated to rate limits, so it misses the highest score.

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?

The description provides no guidance on when to use this tool versus alternatives or in what context it should be invoked. It lacks any mention of prerequisites, timing, or comparisons to other tools, leaving usage entirely implicit.

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/PancrePal-xiaoyibao/get_biji_mcp'

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