Skip to main content
Glama
stackcheck-mcp

stackcheck-mcp

by titouannnn

get_runtime_info

Read-onlyIdempotent

Retrieves current stable, LTS, next LTS, maintained cycles and EOL dates for runtime products from endoflife.date to assess support status.

Instructions

Latest, LTS (lts_eol: true if that LTS is end-of-life), next LTS, maintained cycles and EOL date of the recommended cycle, from endoflife.date. Example: {"products": ["nodejs", "python", "eclipse-temurin"]}

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": {
      "products": "<products>"
    },
    "name": "get_runtime_info"
  }
}

Input Schema

NameRequiredDescriptionDefault
productsYesendoflife.date slugs

Output Schema

NameRequiredDescriptionDefault
staleNo
errorsNo
runtimesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint, so safety and side-effect profile are covered. The description adds that values originate from an external service (endoflife.date) and clarifies the lts_eol flag semantics, but says nothing about behavior for unknown slugs, caching, or whether the 'recommended cycle' is derived.

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

Conciseness3/5

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

There is no filler, but the structure is a comma-separated field inventory ending in the ambiguous phrase 'of the recommended cycle', and the purpose statement is never front-loaded. The reader must assemble the intent from a fragment list plus a parenthetical.

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

Completeness3/5

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

An output schema exists, so return values needn't be spelled out, yet most of the description is spent enumerating them, while the meaning of 'recommended cycle' and behavior on unrecognized products go unexplained. For a one-parameter, read-only lookup this is adequate to call correctly but leaves ambiguity about the result's semantics.

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 100% and the single parameter is already documented as 'endoflife.date slugs', so the baseline would be 3. The description goes beyond it with a concrete example value ({"products": ["nodejs", "python", "eclipse-temurin"]}) that demonstrates the slug format and multiplicity, which the schema alone does not show.

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

Purpose4/5

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

The description names a specific resource and dataset: latest/LTS/next-LTS/maintained cycles and EOL date for runtimes, sourced from endoflife.date. It is phrased as a list of returned fields rather than an explicit verb, so the action ('fetch lifecycle data for these products') must be inferred, but the domain is unmistakable and distinct from a general version lookup.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no exclusions, and no mention of when another tool (e.g. a stack-level check) would be a better choice. The only implicit signal is 'from endoflife.date', which tells the agent the data source but not the selection condition.

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

Deploy Server

Other Tools