Skip to main content
Glama
stackcheck-mcp

stackcheck-mcp

by titouannnn

explain_issue

Read-onlyIdempotent

Fetch declared dependencies, peer dependencies, engines, or parent requirements for a package version to diagnose compatibility issues across npm, PyPI, and Maven.

Instructions

Declared peer deps/engines (npm), requires_dist/requires_python (PyPI) or parent and dependencies (Maven) of one version, to dig into an issue. Example: {"ecosystem": "npm", "package": "typescript-eslint", "version": "8.72.1"}

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": {
      "ecosystem": "<ecosystem>",
      "package": "<package>"
    },
    "name": "explain_issue"
  }
}

Input Schema

NameRequiredDescriptionDefault
packageYesnpm name, PyPI name[extras], group:artifact
versionNodefault: latest stable
ecosystemYes

Output Schema

NameRequiredDescriptionDefault
errorNo
staleNo
extrasNo
parentNo
yankedNo
enginesNo
packageYes
versionNo
ecosystemYes
deprecatedNo
dependenciesNo
optionalPeersNo
requires_distNo
requires_pythonNo
peerDependenciesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/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 the safety profile is covered. The description adds the per-ecosystem return shape, which is genuinely useful context, but says nothing about version resolution behavior, error cases, or what happens with unpublished versions — and an output schema exists to carry return structure.

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?

It is short and the example is compact, but it opens with a noun phrase rather than the action, and the ecosystem parentheticals make the first sentence dense and hard to parse. The example earns its place; the fragment structure does not.

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?

With three parameters, 67% schema coverage, annotations, and an output schema, the definition is adequate but thin. The main gap is routing: an agent cannot determine from this description whether this tool or a sibling is the right call for a dependency investigation.

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 67%, with the package and version parameters already documented (npm name, PyPI name[extras], group:artifact; version defaulting to latest stable). The description contributes a concrete example payload and the 'one version' scoping idea, but adds no syntax or format detail beyond the schema.

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 the specific resource for each ecosystem (peer deps/engines for npm, requires_dist/requires_python for PyPI, parent and dependencies for Maven) scoped to one version, which lets an agent tell what data comes back. The phrasing is a sentence fragment with no leading verb ('explain'), so the action itself is only inferred from the tool name, and it never distinguishes itself from check_stack or get_runtime_info.

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?

The only usage cue is the trailing phrase 'to dig into an issue', which hints at investigation but names no condition, prerequisite, or alternative. Nothing tells the agent when to prefer this over check_stack or get_runtime_info, or when a version argument is required versus optional.

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