Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

Driftline knows when OpenAI, Anthropic and Google retire their models (from their official deprecation pages, checked daily). Call check_models before adding or keeping a model ID in code, and scan_project to audit a codebase.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
check_modelsA

Look up OpenAI, Anthropic and Google model IDs and return, for each one, its retirement status, retirement date, days left and replacement. Use it before writing, changing or keeping a model ID in code, or when the user asks whether a model still works. To find the IDs inside a codebase use scan_project instead; to list everything retiring soon use upcoming_retirements. Read-only. Data comes from the providers' official deprecation pages, re-checked daily at aidriftline.com (fetched with a 4 s timeout, falling back to the copy in the package when offline). IDs not in the registry return status "unknown": no retirement is published for them, which does not prove the ID exists. Up to 100 IDs per call; extra IDs are ignored.

scan_projectA

Scan a project folder for OpenAI, Anthropic and Google model IDs in code and config files and report the ones that are retired, retiring soon, deprecated or being re-routed, with file and line, most urgent first. Use it to audit a repository or before a release. For IDs you already know use check_models; for a time-based list use upcoming_retirements. Read-only: reads files on this machine and never changes them. Scans subfolders recursively, skips .git, node_modules, vendor, dist, build and similar folders, and files over 1 MB. Mentions in .md and .txt files are marked in_docs. Returns at most 200 findings (truncated: true when cut). Fails with an error if the path does not exist.

upcoming_retirementsA

List OpenAI, Anthropic and Google models whose retirement or re-routing date falls in the next N days, soonest first, with replacement for each. Use it to answer "what is being retired soon?" or to plan migrations. It does not look at code: use scan_project for that, or check_models for specific IDs. Read-only. Models already past their date are not included (check_models reports those as retired). Anthropic "not before" dates are left out because those models are still active.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A4.5/5.0

Scored across 3 tools

Disambiguation5/5

Each tool targets a clearly distinct entry point: scan_project audits a codebase, check_models looks up specific known IDs, and upcoming_retirements returns a time-window list. The descriptions explicitly cross-reference each other ("for IDs you already know use check_models"), leaving almost no room for misselection.

Naming Consistency4/5

All snake_case, but two names follow verb_noun (scan_project, check_models) while upcoming_retirements is an adjective_noun phrase describing a list rather than an action. Minor, readable deviation only.

Tool Count4/5

Three tools is a lean surface, but for a narrow read-only domain (AI model retirement auditing) each tool maps to a genuinely different question and none is redundant. Slightly thin, yet well scoped for the purpose.

Completeness4/5

The three access patterns — repo scan, ID lookup, time-based list — cover the core audit and migration-planning workflows with no dead ends. Minor gaps: no registry browsing/filtering by provider, and check_models silently ignores IDs beyond 100 with no paging or batch alternative.

Maintenance

ActivityMaintained
ResponsivenessNo recent community issues