Skip to main content
Glama

Codex Reset Tracker

by dev.tokenusage
OverviewDiscussionsAdmin

Server Details

Codex reset tracker: usage-limit reset announcements from @thsottiaux on X. Read-only, no key.

If you are the author of this connector, you can claim ownership by verifying the domain or GitHub account it belongs to. Claimed connector authors can inspect health checks, view analytics, and manage their listing.
Status
Healthy
Uptime
100.0% over 23 days
Last Tested
Transport
Streamable HTTP · MCP 2025-11-25
URL
Repository
stdcmms-lang/tokenusage-codex-mcp
GitHub Stars
0

TDQS

A3.9/5.0

Scored across 2 tools

Disambiguation4/5

The two tools operate on the same underlying dataset (reset announcements from one X account) but return clearly different shapes: a flat newest-first list versus a date-grouped calendar view. An agent can distinguish them by the grouping/month parameter, though the overlap in content means misuse is still plausible.

Naming Consistency5/5

Both tools follow the same predictable verb_noun pattern with a shared prefix: get_codex_reset_announcements and get_codex_reset_calendar. Fully consistent and readable.

Tool Count3/5

Two tools is thin for the stated scope; the calendar view is largely a re-presentation of the same announcements, so a single tool with a grouping option could suffice. The count is borderline rather than clearly justified.

Completeness3/5

For a read-only mirror of an external source, the chronological and calendar views together cover the core need, but there are no filters (e.g. by resetType), no pagination beyond 50, and no way to fetch a single post by id. Notable gaps for anything beyond casual lookup.

Available Tools

2 tools
get_codex_reset_announcementsCodex reset announcementsA
Read-onlyIdempotent
Inspect

Codex usage-limit reset announcements recorded by tokenusage.dev's Reset Alerts from @thsottiaux's public posts on X, newest first (at most 50): each post's link, when it was posted, when this site recorded it and resetType, plus when the monitor last checked X successfully. 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. Only @thsottiaux is watched. Unofficial, not affiliated with OpenAI. Source: https://tokenusage.dev/resets

NameRequiredDescriptionDefault
limitNoHow many announcements to return, newest first: 1 to 50, default 10.

Output Schema

NameRequiredDescription
resetsYesNewest first.
sourceYesThe 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.
generatedAtYesWhen tokenusage.dev read this data, ISO 8601 UTC. The server caches it for up to 15 seconds.
lastPolledAtYesThe 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.

TDQS

A4/5.0
Behavior5/5

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

Annotations already cover readOnlyHint, idempotentHint, destructiveHint, and openWorldHint, so the bar is lower; the description still adds substantial context beyond them. It explains resetType values (automatic, banked, both, null), clarifies that a banked reset does not itself refill limits, warns that an announcement may be forthcoming or completed and is not proof of a reset, notes that only @thsottiaux is watched, and discloses that the source is unofficial and not affiliated with OpenAI.

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?

The description is front-loaded with the core purpose and is dense with useful information, but it runs long and could be tightened slightly. Every sentence carries meaning, though some readers may find the resetType and banked-reset explanation verbose relative to the single-parameter lookup.

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 read-only tool with one optional parameter and an output schema, the description supplies everything an agent needs: source, uniqueness of the watched account, field meanings, caveats about interpretation, and a pointer to the url for exact wording and eligibility. Nothing critical is missing.

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% – the limit parameter already documents its range (1–50), default (10), and ordering (newest first). The description echoes 'newest first (at most 50)' but adds no additional syntax, format, or behavioral detail beyond what the schema provides, so the 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 states a specific verb (get) and resource (Codex reset announcements), plus the exact source (@thsottiaux's public posts on X) and ordering (newest first, at most 50). It clearly distinguishes what data is returned, but it never mentions the sibling tool get_codex_reset_calendar or explains how the two differ, so an agent must infer the choice.

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 by the resource name and the detailed semantics of resetType and banked resets, but there is no explicit when-to-use/when-not guidance and no alternative tool named. The caveat that 'a post is not proof that any account's limit was reset' hints at interpretation limits, yet it does not route the agent between available options.

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

get_codex_reset_calendarCodex reset calendarA
Read-onlyIdempotent
Inspect

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

NameRequiredDescriptionDefault
monthNoAn optional UTC calendar month, YYYY-MM. Omit it to return every recorded date in the cached response.

Output Schema

NameRequiredDescription
daysYesOnly dates with recorded announcements, newest dates first; at most 50 announcements in total.
monthYesThe requested UTC month, YYYY-MM; null when no month filter was supplied.
sourceYesThe 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.
coverageYesWhat this recorded-announcement calendar covers; missing dates do not establish that no reset was announced.
timeZoneYesCalendar dates are UTC dates.
generatedAtYesWhen tokenusage.dev read this data, ISO 8601 UTC. The server caches it for up to 15 seconds.
lastPolledAtYesThe 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.

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.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

  1. 2 tool updates
    • Changedget_codex_reset_announcements2 fields changed
      • addedOutput schema / properties / resets / items / properties / resetType
        Added value: +{
+  "description": "The monitor's classification of the post: automatic is a direct usage-limit reset with no saved reset; banked is a reset grant saved for eligible users to apply later; both announces both types. Both classifier calls must give the same type. Null means recorded before Reset Alerts recorded reset types. This is not proof that any account's limit was reset.",
+  "enum": [
+    "automatic",
+    "banked",
+    "both",
+    null
+  ],
+  "type": [
+    "string",
+    "null"
+  ]
+}
      • changedOutput schema / properties / resets / items / required
        Previous value: -[
-  "postId",
-  "url",
-  "postedAt",
-  "detectedAt"
-]New value: +[
+  "postId",
+  "url",
+  "postedAt",
+  "detectedAt",
+  "resetType"
+]
    • Addedget_codex_reset_calendar
  2. 1 tool update
    • First observedget_codex_reset_announcements

Related MCP Connectors

Related MCP Servers

  • codex-reset

    suvadadepolo-blip
    A
    license
    Not graded
    quality
    B
    maintenance
    Enables querying forecasts of OpenAI Codex usage-limit resets, verified reset timelines, and current Codex service status through natural language, with no API key required.
    MIT

  • wechat

    zouzhe1
    A
    license
    Not graded
    quality
    A
    maintenance
    Enables OpenAI Codex users to drive coding tasks remotely from their phone chat: sending messages, images, files and voice to Codex, and receiving task-completion notifications with Markdown-formatted results and media. Includes 24-hour window queueing, typing indicators, login/status tools, and watchdog-backed reliability so nothing is silently dropped.
    MIT

  • claude-quota-mcp

    PavolKum
    A
    license
    A
    quality
    B
    maintenance
    Lets an AI agent check its own Claude and Codex usage limits — used percentages and exact reset times for session and weekly windows — so it can plan long-running work around resets instead of dying mid-task. It reads local, credential-free sources by default, always reports which source answered, and ships a hook that pushes quota state into context automatically.
    1
    MIT

  • Claude–Codex Session Link

    Dayc-l
    A
    license
    Not graded
    quality
    B
    maintenance
    Enables Codex to list and read saved Claude Code conversations, retrieve incremental context updates before replies, and optionally ask Claude text-only follow-up questions within a selected session without disrupting the workflow.
    10
    MIT
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.

Resources