DepTime
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DEPTIME_OFFLINE | No | Set DEPTIME_OFFLINE=1 to never touch the network. On first launch DepTime downloads a prebuilt index in the background, then checks for a newer one at most once a day; this disables that behavior. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
DepTime answers "what changed in this Python library, in which release, and what replaces it?" from static analysis of every indexed release (no docs scraping, no LLM guesses). Use it when:
a third-party import or call fails with ImportError, ModuleNotFoundError, AttributeError, or TypeError (unexpected/missing keyword argument): call
explain_errorwith the traceback andpip freezeoutput;you are about to use an API you remember from training data: call
check_symbolswith the installed version;you are upgrading a dependency: call
check_upgradewith the code that uses it for the lines the new version breaks, ordiff_versionsfor every change in the range (from may be a date such as your training cutoff). Callcoverageto see which packages and versions are indexed. Answers include evidence and confidence; "never_existed" means no indexed release ever had that name; at low confidence the name may be created at runtime or predate the earliest indexed release, so read its explanation before calling it misremembered.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| explain_errorA | Call this when a third-party Python library raises ImportError ('cannot import name'), ModuleNotFoundError, AttributeError ('has no attribute'), or TypeError ('unexpected keyword argument' / 'missing required argument'). Returns what changed, in which release, the deprecation message, replacement candidates with evidence, and the version pin that restores the old API. Pass installed versions for an exact answer. An error DepTime can't explain returns empty findings rather than a guess; check |
| symbol_historyA | Version history of one public symbol, e.g. package='httpx', path='httpx.Client.init': first and last release it exists in, signature changes, deprecations, removals, and replacement candidates. Use before writing code against an API you remember from training data. A path no indexed release has is not an error: it returns ever_seen=false. For many symbols at one installed version, use check_symbols. |
| check_symbolsA | Batch-check that symbols, and the keyword arguments you plan to pass, exist in a specific version of a package. Returns present/missing per symbol (unknown where the index can't tell, with the reason), rejected kwargs, deprecation notes, and hints. Use it to preflight code against the version you have installed: pass the symbols, or the code itself. For one symbol across all releases use symbol_history, and after an exception use explain_error. |
| diff_versionsA | Breaking changes and deprecations of a package between two versions, or since a date such as your training cutoff ('YYYY-MM-DD'). Optionally restrict to the symbols your code uses. Most severe first. Use it when upgrading, or for code written against an older release; for a single symbol use symbol_history. |
| check_upgradeA | Call this before or after updating a dependency: pass the package, the version you have, the version you are moving to, and the code that uses the package (a snippet, or several files by path). Returns each use the new version breaks, with its file and line: a removed name, a keyword no longer accepted, a newly required argument, or a call that only raises, with the release that changed it and the replacement. A break is reported only when the new version fails and the old one doesn't; deprecations are warnings, and uses DepTime can't tell about are listed apart, never as breaks. One package per call; for a whole project, |
| coverageA | Lists indexed packages and version ranges. If a package is missing, DepTime cannot answer about it. Takes no arguments; call it first when unsure whether a package is covered. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 6 tools
Most tools have clearly distinct roles: coverage checks indexed packages, explain_error handles runtime exceptions, and check_upgrade validates code against a target version. There is some overlap between check_upgrade and diff_versions, and between check_symbols and symbol_history, but the descriptions explicitly cross-reference each other to guide selection.
The names mix conventions: two use check_ + noun, two use verb_noun, one is a bare noun (coverage), and one is noun_noun (symbol_history). The names are still readable and domain-specific, but there is no predictable pattern across the set.
Six tools is well-scoped for a dependency and API compatibility checking server. Each tool covers a distinct query type (coverage, upgrade breaks, symbol checks, version diffs, runtime errors, symbol history) without obvious redundancy.
The surface covers the full workflow: checking package coverage, preflighting symbols, comparing versions, validating code during upgrades, explaining runtime import/attribute/type errors, and inspecting symbol history. No obvious lifecycle gap remains for the stated dependency compatibility domain.