Skip to main content
Glama
stackexchange-mcp

stackexchange-mcp

by YashLimbani

get_quota_status

Read-onlyIdempotent

Check remaining Stack Exchange API quota and any active rate-limit wait before large searches or when requests fail, so you can avoid or diagnose throttling.

Instructions

Show the remaining Stack Exchange API quota and any active rate-limit wait.

Call this if requests start failing, or before a large batch of searches.

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_quota_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteNoAny valid site slug.stackoverflow

Output Schema

NameRequiredDescriptionDefault
quota_maxYes
authenticatedYes
quota_remainingYes
backoff_seconds_remainingYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

A4/5.0
Behavior3/5

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

The annotations already declare read-only, idempotent and open-world, so the safety profile is covered. The description adds one genuinely useful trait beyond them: the response may report an active rate-limit wait, which tells the agent to back off. It says nothing about whether quota is per-key or per-site, or what the wait means operationally.

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?

Two sentences, the capability statement first and the call trigger second, with no filler. Every clause earns its place.

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?

An output schema exists, so return values need not be explained, and the description covers purpose and timing. The remaining gap is the site parameter and whether quota is global or per-site, which matters before an agent decides how to interpret the result.

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 coverage is 100% for the single optional 'site' parameter with its default, so the schema carries the load. The description never mentions the parameter, which leaves the interesting question open: whether quota is scoped by site at all. Baseline 3 applies when the schema is fully documented.

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?

The description names a specific verb and resource: it shows the remaining Stack Exchange API quota plus any active rate-limit wait. That resource is clearly distinct from the search/lookup siblings, so an agent can tell what it returns without opening the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives two concrete triggering conditions: requests are failing, or a large batch of searches is about to run. It doesn't name an alternative tool or state when not to call it, but for a diagnostic tool the positive triggers cover the realistic use cases.

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