BumpGuard
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
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.
This server publishes no instructions, or was last inspected before Glama recorded them.
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
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| check_upgradeA | Check what breaks in YOUR code when you upgrade a dependency. Call this BEFORE bumping a dependency version. It extracts the real public
API of the currently-installed (or Args: package: Distribution name to upgrade (e.g. "pandas"). to_version: The version you want to move to (e.g. "2.2.0"). code: The source code that uses the package (a file or snippet). from_version: Optional baseline version; defaults to what is installed. language: Ecosystem provider id. Default "python". Returns a report with |
| diff_versionsA | List the API changes between two versions of a package (no code scan). Use this to understand a library's breaking changes in the abstract — e.g. when planning a migration. For "what breaks in my code", use check_upgrade instead. Defaults the baseline to the installed version. |
| verify_snippetA | Verify code against the ACTUALLY-INSTALLED packages to catch hallucinations. Call this after generating code to check that the imports and API calls it uses really exist in this environment. Flags: imported packages that aren't installed (with typo/slopsquat suggestions) and attributes/methods that can't be found on installed modules/classes. Static analysis only — treat 'medium' findings as "verify", not "definitely wrong". |
| check_importA | Check whether a package is installed; if not, suggest close real names. Use this before writing an import to avoid hallucinated or typo'd package names (a common source of slopsquatting risk). |
| list_symbolsA | List the REAL public API (functions/classes/methods + signatures) of a package. Use this to discover the correct API instead of guessing — for the installed
version, or a specific |
| list_languagesA | List the ecosystem providers BumpGuard currently supports. |
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
Each tool targets a distinct operation: checking imports, upgrade impact, version diffs, language listing, symbol listing, and snippet verification. Descriptions explicitly differentiate overlapping use cases, e.g., diff_versions vs. check_upgrade.
All tool names follow a consistent verb_noun pattern in snake_case (e.g., check_import, list_symbols, verify_snippet), making the set predictable and easy to navigate.
Six tools cover the core concerns of dependency safety and API verification without redundancy or excessive granularity. The scope is well-matched to the server's purpose.
The tool surface covers import checking, upgrade impact, API diffing, symbol discovery, and snippet verification. Minor gaps exist (e.g., batch checks or automated fixes), but the core workflow for safe dependency bumps is complete.