Skip to main content
Glama

aihot_get_codex_resets

Read-onlyIdempotent

Get Codex usage-limit resets and reset credits as AIHOT tracks them from Tibo's and Andrew'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_codex_resets"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive and open-world behavior, so the description's extra burden is modest. It does add real context beyond them: that data is sourced from specific people's X posts, that it includes pending announcements, the last 7 days and the last landed reset, and that evidence distinctions must be preserved in the answer.

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. The second sentence about evidence distinctions is instruction-flavored rather than descriptive, but it does convey a real constraint on interpreting the output, so it 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?

For a zero-argument, read-only tool with no output schema, the description covers source, scope, time buckets and the caveat that confirmations, verified receipts and estimates are distinct. It leaves the response shape implicit, which is acceptable given no output schema exists but does require the agent to inspect the result.

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 no schema semantics to add. The description correctly avoids inventing arguments and instead spends its words on what the parameterless call returns.

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 ("Get Codex usage-limit resets and reset credits") plus the data source (Tibo's and Andrew's posts on X). The scope is precise enough to distinguish it from the sibling tools, which retrieve daily/hot-topic/story/search digests rather than Codex reset tracking.

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?

The description implies when the tool applies (questions about Codex reset announcements, recent resets and credits) and names the three time buckets returned, but it never states when not to use it or points to a sibling as an alternative. Guidance is inferable rather than explicit.

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.