Skip to main content
Glama
Sign In
Discord MCP - Discord server management MCP for AI agents

Discord MCP - Discord server management MCP for AI agents

by OrygnsCode
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Get rate limit status

get_rate_limit_status
Read-only

Monitor Discord rate-limit hits and invalid-request counts so you can see when calls feel slow and avoid temporary IP bans from too many invalid responses.

Instructions

How rate limiting has been going: how many times Discord asked this server to slow down (the request layer waits automatically), and the invalid-request counter that matters because Discord temporarily bans an IP after 10,000 invalid responses in ten minutes. Useful when calls feel slow.

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": "get_rate_limit_status"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.4.2
    • addedInput schema / $schema
      Added value: +"https://json-schema.org/draft/2020-12/schema"
  2. First observedv1.0.2

TDQS

A3.8/5.0
Behavior4/5

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

Beyond readOnlyHint=true, the description discloses real operational context: the request layer waits automatically rather than erroring, and Discord temporarily bans an IP after 10,000 invalid responses in ten minutes. That explains why the invalid-request counter matters, which annotations cannot convey. It stops short of describing the response shape or how to interpret threshold proximity.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single compact sentence-pair that front-loads the two counters and ends with the practical trigger. The informal framing ('How rate limiting has been going') costs a little precision, but no sentence is filler.

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?

With no input parameters and no output schema, the description carries the burden of explaining return values, and it does describe both counters qualitatively and the consequence of overflow. It does not give field names or a concrete shape, which leaves a minor gap for a schema-less response.

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 takes no parameters, so there is nothing for the description to disambiguate; the baseline for a zero-parameter tool applies. The prose stays focused on what the counters mean rather than inventing parameter-like details.

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 identifies the resource as rate-limit status and names the two things it reports: the count of slow-down requests and the invalid-request counter. It lacks a crisp verb phrase like 'Returns' and the opening clause ('How rate limiting has been going') is chatty, but an agent still knows exactly what the call yields. No sibling covers rate limits, so differentiation isn't needed.

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?

It supplies one concrete trigger — 'Useful when calls feel slow' — which is genuinely actionable for diagnosing throttling. There is no guidance on when not to call it, or on whether to check it proactively versus only after a failure. Usage is implied rather than systematized.

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