Skip to main content
Glama

rate_limit_status

Read-onlyIdempotent

Check remaining request budget in the client's local sliding window before making calls. Returns session rate-limit status without a network request.

Instructions

Remaining request budget in the client's local sliding window. No network call.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, and non-destructive, so the safety profile is covered. The description adds genuinely new behavioral context beyond that: the budget is measured against a 'local sliding window' on the client, not authoritative server state, and the call is free of network cost. It stops short of saying whether or how the window resets or how coarse the remaining count is.

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 short sentences, zero filler, with the primary fact (what is measured) front-loaded and the operational caveat second. Nothing could be cut without losing information.

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?

For a zero-parameter local read with no output schema, the definition covers what the tool reports and where the number comes from. The main remaining gap is the shape of the return value — whether it includes a reset time, a raw count, or a ratio — which no output schema documents either.

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 the baseline is 4 and there is nothing for the description to disambiguate. It correctly doesn't waste words restating an empty schema.

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 names the specific resource queried — the remaining request budget in the client's local sliding window — so an agent knows exactly what it gets back. It doesn't need to differentiate from the listed siblings (contact tools, governance) since none overlap, but it also doesn't frame itself as a status/introspection call explicitly.

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?

There is no explicit when-to-use statement or named alternative; usage is only implied by 'No network call', which hints the tool is cheap enough to consult before issuing real requests. An agent can infer the use case but must do the reasoning itself.

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