EndOfLife 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 |
|---|---|
| list_productsA | Browse all software products tracked for end-of-life information. Use this as your starting point to discover what products are available, or when you need to help users find software they're asking about. Returns product names, descriptions, and basic metadata. |
| get_productA | Get comprehensive end-of-life information for a specific software product. Returns all release cycles, support dates, and EOL status. Perfect for answering questions like 'When does Python 3.8 reach end-of-life?' or 'What Ubuntu versions are still supported?' |
| get_product_releaseA | Get detailed information about a specific version/release of a product. Use this when you need precise details about one particular version, such as exact end-of-life dates, support status, or the latest patch version available. |
| list_categoriesA | Discover how products are organized by category. Returns categories like 'os' (operating systems), 'lang' (programming languages), 'db' (databases), 'server-app' (server applications), etc. Use this to understand the taxonomy or to help users explore related products. |
| get_category_productsA | Find all products within a specific category. Useful for comparative analysis or when users ask broad questions like 'What databases are tracked?' or 'Show me all the operating systems.' Much more focused than browsing all products. |
| list_tagsC | Explore products by tags/labels that describe their characteristics. Tags provide a different organizational system than categories, often describing technical attributes, company associations, or use cases. |
| get_tag_productsA | Find all products that share a common tag. Useful for discovering related technologies or when users want to see all products from a specific vendor or with particular characteristics. |
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 7 tools
Every tool has a clearly distinct purpose with no ambiguity: get_category_products filters by category, get_product retrieves detailed EOL info for a specific product, get_product_release focuses on a single version, get_tag_products filters by tags, list_categories shows available categories, list_products lists all products, and list_tags shows all tags. The descriptions explicitly differentiate their scopes, making misselection unlikely.
All tools follow a consistent verb_noun pattern using snake_case: get_*, list_*. The verbs 'get' and 'list' are used predictably—'get' for retrieving specific items and 'list' for browsing collections. There are no deviations in naming conventions across the set.
With 7 tools, this server is well-scoped for its purpose of querying end-of-life information. Each tool earns its place by covering distinct aspects of the domain: browsing (list_*), filtering (get_* by category/tag), and detailed retrieval (get_product, get_product_release). The count is neither too thin nor overwhelming.
The tool set provides complete coverage for the EOL domain, enabling agents to explore categories and tags, browse all products, filter by category or tag, retrieve detailed product info, and drill down to specific releases. There are no obvious gaps; agents can navigate from broad discovery to precise queries without dead ends.