Codex Reset Tracker

Codex reset calendar

get_codex_reset_calendar

Read-onlyIdempotent

Codex usage-limit reset announcements recorded by tokenusage.dev's Reset Alerts from @thsottiaux's public posts on X, grouped by UTC calendar date, newest dates first, with posts within each date newest first (at most 50 announcements in total). Optional month selects a UTC month written YYYY-MM. Dates are UTC; only dates with recorded announcements are returned. Only announcements this monitor recorded from @thsottiaux are shown, at most the 50 newest; this is not a complete history. A date without an entry does not mean no reset was announced. Each item has postId, url, postedAt and resetType. resetType is automatic, banked or both; null means recorded before Reset Alerts recorded reset types. A banked reset grant saves a reset for eligible users to apply later and does not itself refill limits. An announcement may describe a forthcoming event or one already completed; a post is not proof that any account's limit was reset. Open its url for the exact wording and eligibility. Unofficial, not affiliated with OpenAI. Source: https://tokenusage.dev/resets

Input Schema

Name	Required	Description	Default
`month`	No	An optional UTC calendar month, YYYY-MM. Omit it to return every recorded date in the cached response.

Output Schema

Name	Required	Description
`days`	Yes	Only dates with recorded announcements, newest dates first; at most 50 announcements in total.
`month`	Yes	The requested UTC month, YYYY-MM; null when no month filter was supplied.
`source`	Yes	The fixed credit URL, https://tokenusage.dev/resets. When showing the data to other people, show Data: tokenusage.dev linked to this URL on the same screen or in the same message. Personal use needs no visible credit. API and MCP relays must retain source and pass on this credit condition.
`coverage`	Yes	What this recorded-announcement calendar covers; missing dates do not establish that no reset was announced.
`timeZone`	Yes	Calendar dates are UTC dates.
`generatedAt`	Yes	When tokenusage.dev read this data, ISO 8601 UTC. The server caches it for up to 15 seconds.
`lastPolledAt`	Yes	The monitor's latest successful fetch of @thsottiaux's X timeline, checks that found no new posts included, ISO 8601 UTC; null before the first, or when an older record lacks it. It is not a sign that classification or alert delivery is working.

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 10, 2026

TDQS

A3.9/5.0

Behavior5/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), and the description still adds substantial behavioral context: the 50-item cap, that this is not a complete history, that a missing date does not mean no reset, resetType semantics including 'banked', and the caveat that a post is not proof of a reset. This is rich disclosure well beyond the structured fields.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The scoping and date-grouping are front-loaded, which is good, but the text is bloated with repetition: the 50-announcement cap is stated twice and UTC is stated twice, and item fields are enumerated despite an output schema. Several sentences could be merged without losing meaning.

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 zero-required-parameter read tool with an output schema, the description leaves nothing essential uncovered: source, coverage limits, semantics, and disclaimers are all present. Any remaining redundancy is a conciseness issue, not a completeness gap.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100% and the schema already documents the month format and omission behavior, so the description largely restates it. It adds minor meaning by confirming UTC and that only dates with announcements are returned. Baseline 3 is appropriate.

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 gives a precise verb and resource: reset announcements from a specific source, grouped by UTC date, newest first. It is easy to tell this is a date-grouped calendar view rather than a flat list. It stops short of naming or contrasting with the sibling get_codex_reset_announcements, so 5 is not warranted.

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?

It explains the optional month parameter and what omission does, implying when to add a filter. However, there is no explicit when-to-use-this-vs-the-sibling routing, and no stated exclusions or alternatives. Usage is implied rather than directed.

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

All Codex Reset Tracker tools Inspect

Try in Browser

Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.