EOL MCP Server
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| check_versionB | Check EOL status and support information for software versions |
| check_cveC | Scan for known security vulnerabilities and support status |
| list_productsC | Browse or search available software products |
| compare_versionsC | Compare versions and get detailed upgrade analysis |
| get_all_detailsB | Get comprehensive lifecycle details for all versions of a product |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| check_software_status | Check if software versions are supported and get EOL dates |
| compare_versions | Compare versions and analyze upgrade recommendations |
| analyze_security | Comprehensive security analysis including EOL status and vulnerabilities |
| natural_language_query | Process natural language queries about software lifecycle |
| validate_version | Validate version recommendations before responding |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 5 tools
Each tool has a clearly distinct purpose with no ambiguity: list_products for browsing, get_all_details for comprehensive lifecycle info, check_version for EOL status, compare_versions for upgrade analysis, and check_cve for security scanning. The descriptions clearly differentiate their functions, making misselection unlikely.
All tools follow a consistent verb_noun pattern with snake_case naming (e.g., list_products, check_version, compare_versions). The naming is predictable and readable throughout the set, with no deviations in style or convention.
With 5 tools, this server is well-scoped for its EOL and software lifecycle management purpose. Each tool earns its place by covering distinct aspects of the domain, from product listing to detailed analysis, without being too sparse or bloated.
The tool set provides complete coverage for the domain, including browsing products, retrieving lifecycle details, checking EOL status, comparing versions for upgrades, and scanning for vulnerabilities. There are no obvious gaps, and the tools support a full workflow from discovery to analysis.