Skip to main content
Glama

List rate limits

list_rate_limits
Read-only

Use this when a call was refused for too many calls, or before a large run of calls, to see every rate limit the organization's calls share and how much of each is left in the current window. Also returns today's spend against the daily cap. Free, and reading it never uses up a limit.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.5/5.0
Behavior4/5

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

The annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so safety is covered by structured data. The description nonetheless adds genuinely useful, non-obvious context: the call is free and reading it never consumes a limit, which matters enormously for a tool an agent may invoke while throttled. It omits other traits such as auth requirements or window/reset semantics, keeping it below the top of the scale.

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, front-loaded with the triggering condition and followed by what is returned and the cost implication. Nothing is redundant and every clause carries information an agent would act on.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a no-parameter, read-only inspection tool with no output schema, the description covers trigger, scope of results, and cost behavior — everything needed to decide to call it and interpret the result. Given the annotations already carry the safety profile, no material gap remains.

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 zero parameters, so there is no parameter meaning to explain and the baseline is 4. The schema is empty and fully consistent with the description, which asks for no inputs.

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?

States a specific verb-and-resource pair (list every rate limit the organization's calls share) plus the exact payload: remaining quota per limit in the current window and today's spend against the daily cap. That level of specificity lets an agent tell it apart from the campaign/list management siblings 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?

Gives two concrete triggering conditions — reactively after a refusal for too many calls, and proactively before a large run of calls — which is strong when-to-use guidance. It stops short of naming any alternative tool to consult instead (e.g. list_api_requests) or stating when not to bother, so it is clear but not exhaustive.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources