Skip to main content
Glama

endoflife.ai — Software Lifecycle Intelligence

Scan a stack

scan_stack
Read-onlyIdempotent

Audit a whole stack at once. Provide a list of products (optionally with versions) — e.g. parsed from a package.json or Dockerfile — and get an EOL Risk Score for each, so you can see what is unsupported and dangerous in one call. For CycloneDX or SPDX documents use check_sbom instead. Without an API key up to 5 items are checked per call; items beyond it are listed as not checked, with a note.

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": {
      "items": "<items>"
    },
    "name": "scan_stack"
  }
}

Input Schema

NameRequiredDescriptionDefault
itemsYesList of stack components to score.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, closed-world, non-destructive behavior, so the description only needs to add what annotations can't. It does exactly that: a hard cap of 5 items per call without an API key, and that overflow items are returned as 'not checked' with a note — critical behavior for an agent building a call.

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?

Three sentences, front-loaded with the action and the alternative-routing second. The clause 'so you can see what is unsupported and dangerous in one call' is slightly redundant with 'EOL Risk Score' but still reinforces intent; nothing else is wasted.

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 single-parameter batch tool with an output schema and full annotation coverage, the description supplies the remaining decision-critical facts: input shape provenance, when to route to check_sbom, and the unauthenticated 5-item truncation behavior.

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

Parameters3/5

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

Schema coverage is 100% and the nested item properties already document product and the optional version (including 'omit for highest-risk release'). The description only adds provenance context (items typically parsed from package.json or Dockerfile), which is marginal beyond the schema.

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?

The description uses a specific verb and resource ('Audit a whole stack at once'), says it returns an EOL Risk Score per item, and gives concrete input provenance (package.json, Dockerfile). It also differentiates itself from the sibling check_sbom by naming it for CycloneDX/SPDX inputs.

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?

It clearly states the use case (bulk auditing of a list of products) and names an explicit alternative for SBOM documents via check_sbom. It does not contrast with check_eol for single-product lookups, but the 'whole stack at once' framing makes the batch scope evident.

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.