Skip to main content
Glama
modelanalyzer-mcp

modelanalyzer-mcp

by yeaske

Upcoming model retirements

model_retirements
Read-only

Look up announced API shutdown dates for tracked AI models and get each maker's recommended replacement.

Instructions

Announced API shutdown dates for tracked models, with each maker's recommended replacement.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile and the live/external nature of the data are covered. The description adds useful content context (announced dates plus maker-recommended replacements) but says nothing about freshness, ordering, or whether retired/already-shutdown models appear — details an agent would want for open-world data.

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

Conciseness5/5

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

A single front-loaded sentence that states the resource first and the extra payload second, with no filler or restated name.

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-parameter, read-only lookup with no output schema, the definition gives enough to call it correctly and know roughly what comes back (dates plus replacement suggestions). The only remaining gap is scope/timeliness of 'tracked models', which keeps it from being fully complete.

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 no parameters, so the baseline is 4 and the schema burden is nil. The description correctly implies a parameterless full listing rather than a filtered query, leaving no ambiguity about required inputs.

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 names a specific resource (announced API shutdown dates for tracked models) and states the payload includes each maker's recommended replacement, which is concrete enough to distinguish it from compare_models, estimate_cost, recommend_models and search_models. It is not a tautology of the name, though 'tracked models' leaves the scope slightly open.

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 only implied: an agent can infer this is the tool for checking deprecation timelines and migration targets. There is no explicit statement of when to prefer it over siblings such as recommend_models (for replacement choice) or search_models, and no mention of whether past retirements are included.

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