Skip to main content
Glama

AI model deprecation and retirement dates, by provider

Which AI models shut off in the next N days?

upcoming_retirements
Read-only

What is about to break? Lists the model ids whose provider has published a shutdown date inside the next N days, soonest first, each with the provider, the replacement it names and a verbatim quote. Use it to sweep a codebase's pins before they bite, or to see what a quarter's migration work looks like. Optionally narrowed to one provider. Dates a provider printed as a floor ("not sooner than") are deliberately left out and counted in the response, because such a model could go years later and listing it here would be a guess.

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

Input Schema

NameRequiredDescriptionDefault
daysNoHow far ahead to look, in days from today (UTC). 90 by default. Pass 0 to get only what is already past its date.
limitNoHow many to return, 1–20. Default 20.
providerNoOptional case-insensitive substring of the provider name ("openai", "bedrock", "azure", "together").
include_already_retiredNoInclude models whose shutdown date has already passed. False by default: this tool answers "what is coming". Set true to audit pins that are already dead.

Output Schema

NameRequiredDescriptionDefault
toYes
fromYes
as_ofYes
modelsYes
coverageYes
registerNo
window_daysYes
models_matchedYes
models_returnedNo
excluded_floor_datesNoHow many records fell in the window only on a date the provider printed as a floor ("not sooner than"), and were therefore left out. Reported so the omission is visible instead of silent.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, non-destructive and closed-world, so safety is covered. The description adds genuinely useful behavior beyond that: result ordering, the deliberate exclusion of floor-dated shutdowns with an explanation and a note that they are counted in the response. It does not discuss pagination or truncation when more than limit match, which is the main remaining behavioral gap.

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?

Front-loaded with the core question and answer, then use cases, then the exclusion rule. Slightly rhetorical framing ("What is about to break?", "before they bite") but no sentence is wasted; the closing sentence on floor dates carries real information.

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 an output schema, full param coverage and annotations, the description only needs to carry scope and intent, and it does: what is included, what is deliberately excluded, ordering, and typical uses. Minor gaps around behavior at the result cap and how the exclusion count surfaces are acceptable given the output schema.

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 spells out days (default 90, 0 = already past), limit range, provider substring matching and include_already_retired semantics. The description only restates the N-day window and single-provider narrowing, adding no format or edge-case detail the schema lacks. Baseline 3 applies.

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?

States a precise verb-and-resource: lists model ids whose provider published a shutdown date within the next N days, with ordering (soonest first) and per-item payload (provider, replacement, verbatim quote). The exclusion of "not sooner than" floor dates further sharpens scope. It never names or contrasts with the siblings model_status / verify_quote, so sibling differentiation is left to inference.

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 concrete use cases: sweeping a codebase's pins before they bite, or sizing a quarter's migration work; and notes optional narrowing to one provider. It stops short of explicit when-not guidance or pointing to model_status when an agent wants a model's current state rather than a forecast.

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.

Resources