Skip to main content
Glama
NY5184

dependency-health

by NY5184
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
dependency_health_checkA

Analyzes project dependencies and provides contextual data to assess upgrade impact.

Supports: npm (package.json) and pip (requirements.txt) only. Other package managers (Poetry, Pipenv, Cargo, Go modules, Maven, Gradle, Composer, NuGet, etc.) are not supported.

Returns for each dependency: name, current version, latest version, status, changelog_content (actual release notes or explanatory message), description, and release_date.

When to use this tool:

  • User asks about dependency versions/updates in a specific project

  • User requests dependency health check or audit

  • Before suggesting upgrades that require inspecting actual project dependencies

How to analyze results:

  1. Use changelog_content to identify specific changes, bug fixes, breaking changes

  2. State that assessment is limited if changelog could not be fetched

  3. Direct user to source URL if mentioned in changelog_content

  4. Do not infer changes not explicitly stated in changelog_content

  5. Use description and release_date to assess maturity/stability

  6. Consider major version gaps as potential breaking change indicators

Provide recommendations (low/medium/high impact) based on risk, scope, and maintenance implications—not just version differences.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A3.6/5.0

Scored across 1 tool

Disambiguation5/5

With only one tool, there is no risk of confusion between tools. The single tool's purpose is clearly defined.

Naming Consistency5/5

The tool name 'dependency_health_check' uses a clear snake_case convention, which is consistent with common naming practices. With only one tool, consistency is not an issue.

Tool Count4/5

The single tool covers the core function of dependency health checking, but the scope is narrow (only npm and pip). The count is slightly below the typical range but still reasonable for a focused utility.

Completeness2/5

The tool only supports npm and pip, leaving out many common package managers (e.g., Cargo, Go modules, Maven). This is a significant gap that limits the tool's usefulness for projects using other managers.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources