Skip to main content
Glama

Get rate limit status

get_rate_limit_status
Read-onlyIdempotent

Check cached Inoreader API rate-limit status, reset/cooldown times, and conservative local usage estimates without spending HTTP or auth requests.

Instructions

Check cached quota observations, reset/cooldown times and conservative local estimates. Costs 0 HTTP/auth requests. Header usage is authoritative only at observation time; missing/expired values mean unknown, not free calls. Every attempted API fetch (including retries and failures) is counted locally; other clients/processes are unseen. See inoreader://usage for request costs, URI examples and all workflow prompts.

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.6.1
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  2. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare read-only, non-destructive, idempotent and closed-world, so the bar is lower, yet the description adds substantial caveats the annotations cannot: cost is zero, header values are only authoritative at observation time, missing/expired means unknown rather than free, and local counting misses other clients. That is exactly the calibration context an agent needs before trusting the output; it stops short of five only because the returned shape is not characterized.

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?

Front-loaded with the action and its cost, then caveats, then a pointer to further docs — a sensible order with no filler sentences. The trailing inoreader://usage reference is slightly tangential but earns its place by bundling costs, URI examples and prompts.

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?

For a no-param read tool with annotations covering the safety profile, the description covers caveats well, but with no output schema an agent still does not know what fields the "quota observations" contain or how to interpret numbers against limits. That gap keeps it at adequate rather than complete.

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 schema-layer baseline of 4 applies and the description's reference to reset/cooldown times gives a sense of what values matter. No parameter meaning is left ambiguous because there are none.

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 ("Check") and three concrete resources (cached quota observations, reset/cooldown times, conservative local estimates), and immediately frames them as cached/local rather than live. No sibling tool in the list touches quota at all, so an agent can place it unambiguously.

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?

"Costs 0 HTTP/auth requests" strongly implies this is the safe pre-flight check before attempting real fetches, and the inoreader://usage pointer offers further context. However, it never explicitly states when to call it versus alternatives or which workflows require it, leaving the usage decision inferential.

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