Skip to main content
Glama
Sign In
Tech Debt MCP Server

Tech Debt MCP Server

by viniciosrab
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

check_dependencies

Analyze project dependencies across multiple package managers to surface technical debt, with an option to include development dependencies.

Instructions

Analyze project dependencies across multiple package managers.

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": {
      "path": "<path>"
    },
    "name": "check_dependencies"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYesAbsolute path to the project root directory
includeDevNoOptional: include development dependencies (default: true)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.1

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full disclosure burden, and it says nothing about whether the tool only reads, whether it touches the network or lockfiles, which package managers are detected, or whether it modifies the project. 'Analyze' hints at read-only behavior but never states it, which is a notable gap for a tool with no annotation coverage.

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?

It is a single front-loaded sentence with no filler, which is efficient. The brevity edges into under-specification rather than verbosity, but nothing is redundant.

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

Completeness2/5

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

With no annotations and no output schema, the definition must convey behavior and results on its own, and it does not: the agent does not know what the analysis returns, how package managers are discovered, or how failures are surfaced. For a multi-ecosystem analyzer, this is thin.

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 both 'path' (absolute project root) and 'includeDev' (default true) are already fully documented in the schema. The description adds nothing about parameter behavior, such as what 'includeDev' changes in the analysis output, so the baseline 3 applies.

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 verb-plus-resource ('Analyze project dependencies') and adds a scope qualifier ('across multiple package managers'). It is clear what the tool does, but it never distinguishes itself from the closest siblings ('analyze_project', 'analyze_file'), so an agent must infer whether this is a subset or a separate concern.

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 or when-not-to-use guidance, and no alternative is named. Given the presence of 'analyze_project' and 'analyze_file' in the catalog, the agent is left to guess whether this duplicates part of those tools or complements them.

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