Skip to main content
Glama
Sign In
MCP Hub

MCP Hub

by airano-ir
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

reset_rate_limit

Reset rate limit state for a client or all clients to clear throttling. Administrative tool for removing rate limits.

Instructions

Reset rate limit state for a client or all clients.

CAUTION: This is an administrative tool. Use with care.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "reset_rate_limit"
  }
}

Input Schema

NameRequiredDescriptionDefault
client_idNoOptional client identifier to reset. If not provided, resets ALL clients.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv3.13.1
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / client_id / description
      Added value: +"Optional client identifier to reset.\n       If not provided, resets ALL clients."
  2. First observedv3.4.0

TDQS

B3.3/5.0
Behavior2/5

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

No annotations provided, so the description must fully disclose behavior. It warns that the tool is administrative but does not explain what resetting entails (e.g., clearing all counters, potential impact on clients). Missing details on reversibility, permissions required, or side effects.

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?

Extremely concise: two short sentences. The first sentence directly states the purpose, and the second provides a critical caution. No unnecessary words or repetition.

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?

Adequately covers the basic functionality and includes a caution, but for an administrative tool, more context about impact, safety, and typical use cases would be valuable. The output schema may describe return values, but behavioral context is missing.

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 description does not add meaning beyond the schema. The schema already describes 'client_id' as optional with a default of null and explains that omitting it resets all clients. With 100% schema coverage, the baseline is 3, and no extra parameter insight is provided.

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?

Clearly states the action (reset), resource (rate limit state), and scope (client or all clients). The purpose is unambiguous and distinguishes this tool from siblings that deal with health, metrics, or WordPress operations.

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 only guidance is 'CAUTION: This is an administrative tool. Use with care.' This lacks explicit instruction on when to use this tool versus alternatives, such as when rate limits are misconfigured or need to be cleared. No mention of prerequisites or consequences.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools