Skip to main content
Glama

Which base images in this Dockerfile are out of support?

Is this Python, Node.js or Ubuntu release still supported?

release_support_status
Read-only

One release, without a Dockerfile. Give a product ("Python", "Node.js" or "Ubuntu") and a release — a number like "3.9", "22.04" or Node's "18", or an Ubuntu codename like "jammy" — and get its release date, its end of active support, its end of security support, Ubuntu's paid extended window where there is one, and a verbatim quote of the vendor's own published line. A release this register does not hold returns found: false rather than a guess.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "product": "<product>",
      "release": "<release>"
    },
    "name": "release_support_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
productYes"Python", "Node.js" (also "node", "nodejs") or "Ubuntu", case-insensitive.
releaseYes"3.9", "3.11.9", "22.04", a Node.js major such as "18" or "v18.17.0", or an Ubuntu codename such as "jammy".

Output Schema

NameRequiredDescriptionDefault
noteNo
foundYes
releaseNo
coverageYes
registerNo
products_we_holdNo
newest_supported_release_we_holdNoOURS, computed from these records; no source here names a successor.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds useful behavior beyond that: the specific fields returned (release date, active/security EOL, paid extended window, verbatim vendor quote) and the found:false fallback for unknown releases. It does not discuss rate limits or data freshness, so a 3 is appropriate.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two dense sentences, front-loaded with the scope constraint and then the input/output contract. Every clause carries information, though the enumeration of returned fields is slightly long for a tool that also has an output schema.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a two-parameter read-only lookup with a full output schema, the description covers inputs, accepted formats, return contents, and the not-found case. Nothing an agent needs in order to call it correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is already 100%, so the baseline is 3, but the description adds real meaning: it clarifies that release accepts a bare number, a full version, a Node major, or an Ubuntu codename, and that product is one of three named values. This reinforces and slightly extends the schema's own examples.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource (look up one release's support status) and immediately distinguishes itself from the sibling with 'One release, without a Dockerfile.' An agent can tell this apart from check_dockerfile without opening either schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explains the required inputs and the not-found behavior ('returns found: false rather than a guess'), and the opening clause implies the alternative (Dockerfile-based checking). It stops short of an explicit 'use this when / use check_dockerfile when' statement, so it is clear context rather than full routing guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources