Skip to main content
Glama

aihot_get_grok_bot_resets

Read-onlyIdempotent

Get Grok Bot usage-limit resets and reset credits as AIHOT tracks them from @bot's posts on X: announcements still waiting to take effect, the last 7 days and the last landed one, each with its evidence. Keep the evidence distinctions in the answer: a confirmation post, a verified receipt and an estimate are different things.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, open-world and non-destructive behavior, so the description only needs to add context. It does: it discloses the provenance (tracked from @bot's posts on X), the 7-day window, that some entries are pending and may not take effect, and that evidence types (confirmation post, verified receipt, estimate) must be kept distinct.

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?

Two sentences, front-loaded with the verb and resource, with the retention rule stated second. The second sentence is dense but earns its place as a result-handling constraint; the only mild excess is the slightly run-on enumeration of the three time buckets.

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 parameters and no output schema, the description has to sketch the return shape, and it does so at a usable level: pending items, the last 7 days, and the last landed reset, each carrying evidence. It stops short of describing field-level structure, but an agent can plan a call from it.

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. Baseline 4 applies because no parameter semantics are needed at all.

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 a specific verb and resource ('Get Grok Bot usage-limit resets and reset credits') plus the data source (@bot's posts on X), so the agent knows exactly what it retrieves. Product naming implicitly separates it from the sibling per-product reset tools, but it never explicitly routes to them.

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?

Usage is implied rather than stated: the content breakdown (pending announcements, last 7 days, last landed) suggests when the data is relevant, but there is no explicit 'use this when' or 'use aihot_get_claude_resets instead' guidance.

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.