Skip to main content
Glama
stackcheck-mcp

stackcheck-mcp

by titouannnn

check_stack

Read-onlyIdempotent

Resolve stable npm, PyPI, and Maven package versions and detect incompatibilities between them in one call, returning suggested fixes plus runtime support and dependency declarations.

Instructions

Latest stable versions plus incompatibilities between the packages and their shared deps (peer deps, requires_dist, engines, requires_python, wheels, BOM). Example: {"npm": ["react", "typescript", "typescript-eslint", "vite@^8"], "pypi": ["fastapi"]}

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "check_stack"
  }
}

Input Schema

NameRequiredDescriptionDefault
npmNoname or name@range
pypiNoPEP 508, extras ok
mavenNogroup:artifact[:version|range]
targetsNocycle or version; default Node LTS, newest Python, Java LTS
runtimesNoendoflife slugs
maven_bomNoBOM group:artifact[:version]

Output Schema

NameRequiredDescriptionDefault
npmNo
pypiNo
mavenNo
staleNo
errorsNo
issuesNo
targetsNo
runtimesNo
warningsNo
validationNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already establish read-only, idempotent, open-world behavior, so the safety profile is covered. The description adds that results include cross-dependency incompatibility analysis across named ecosystems and lockfile-ish artifacts (BOM, wheels), but never says it resolves against live registries or how staleness/latest is determined.

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?

The purpose is front-loaded in a single dense sentence, and the JSON example is compact and illustrative rather than padded. Minor redundancy with the schema's example-shaped parameters, but it earns its space by anchoring the call format.

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 need no explanation, and the multi-ecosystem scope is named. Still, with six optional parameters governing targets/runtimes/BOM, the description doesn't explain what those switches change about the analysis, which is a notable gap for a tool of this complexity.

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 description coverage is 100%, so the baseline is 3. The description's example shows the accepted string shape for npm and pypi entries but adds nothing for maven, targets, runtimes, or maven_bom, leaving the schema's own descriptions to carry those.

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?

States a specific verb+resource: it returns latest stable versions and flags incompatibilities across declared dependency types (peer deps, requires_dist, engines, requires_python, wheels, BOM). That is materially more informative than the bare name, but it draws no boundary against get_runtime_info, which plausibly also covers runtimes/endoflife data.

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

Usage Guidelines3/5

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

Usage is only implied: the example payload demonstrates a typical npm+pypi call, which signals intended scenarios without saying when to prefer this tool over get_runtime_info or explain_issue. There are no exclusion criteria or prerequisites stated.

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