Skip to main content
Glama
Sign In

AIHOT

by io.github.KKKKhazix
OverviewDiscussionsAdmin

aihot_get_claude_resets

Read-onlyIdempotent

Get Claude usage-limit resets and reset credits as AIHOT tracks them from ClaudeDevs's and Lydia'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_claude_resets"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/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, open-world behavior, and the description does not contradict them. It adds genuinely new context: the data originates from social posts, is organized into pending/recent/last-landed buckets, and carries differing evidence types (confirmation post vs verified receipt vs estimate). It stops short of discussing staleness, refresh cadence, or empty-result behavior.

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 resource and source, then the data buckets. The enumeration in sentence one ('announcements still waiting to take effect, the last 7 days and the last landed one') is dense but each clause carries meaning; nothing is filler.

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 input parameters, no output schema, and simple read-only annotations, the description covers the essentials: what is returned, where it comes from, and how to interpret evidence tiers. The only gap is the concrete response shape, which is defensible to omit given the description names the top-level buckets.

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 there is no parameter semantics to document and the baseline of 4 applies. The description does not waste space restating schema content that does not exist.

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 Claude usage-limit resets and reset credits') plus the data provenance ('as AIHOT tracks them from ClaudeDevs's and Lydia's posts on X'). The 'Claude' qualifier clearly separates it from the sibling reset tools for Codex and Antigravity.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives clear usage context: the tool returns pending announcements, the last 7 days, and the last landed reset, and it instructs the agent to preserve evidence distinctions when answering. It does not, however, state exclusions or explicitly route to `aihot_get_codex_resets` / `aihot_get_antigravity_resets` for other providers.

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

All AIHOT toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources