Skip to main content
Glama
code-alchemist01

Development Tools MCP Server

check_outdated_packages

Identify outdated dependencies in your project to maintain code security and compatibility. Scans package files to detect versions requiring updates.

Instructions

Check for outdated packages

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
projectPathNoPath to project root

Implementation Reference

  • Executes the tool logic by analyzing project dependencies specifically for outdated packages using DependencyAnalyzer and returns the outdated list with count.
    case 'check_outdated_packages': {
      const report = await analyzer.analyzeDependencies(projectPath, {
        checkUnused: false,
        checkOutdated: true,
        checkVulnerabilities: false,
      });
      return {
        outdated: report.outdated,
        total: report.outdated.length,
      };
    }
  • Defines the tool's name, description, and input schema (projectPath parameter).
    {
      name: 'check_outdated_packages',
      description: 'Check for outdated packages',
      inputSchema: {
        type: 'object',
        properties: {
          projectPath: {
            type: 'string',
            description: 'Path to project root',
          },
        },
      },
    },
  • src/server.ts:18-25 (registration)
    Includes dependencyAnalysisTools (containing check_outdated_packages) in the complete list of tools registered with the MCP server.
    const allTools = [
      ...codeAnalysisTools,
      ...codeQualityTools,
      ...dependencyAnalysisTools,
      ...lintingTools,
      ...webScrapingTools,
      ...apiDiscoveryTools,
    ];
  • src/server.ts:66-67 (registration)
    Dispatches tool calls matching dependencyAnalysisTools (including check_outdated_packages) to the specific handler function.
    } else if (dependencyAnalysisTools.some((t) => t.name === name)) {
      result = await handleDependencyAnalysisTool(name, args || {});
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only states the action ('Check') without details on permissions, output format, rate limits, or whether it's read-only or destructive. This is inadequate for a tool with potential behavioral implications.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, efficient sentence with no wasted words. It is appropriately sized and front-loaded, making it easy to parse quickly.

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?

Given the tool's potential complexity (checking packages in a project) and lack of annotations or output schema, the description is incomplete. It doesn't explain what 'outdated' means, how results are returned, or any behavioral traits, leaving significant gaps for the agent.

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?

The input schema has 1 parameter with 100% description coverage ('Path to project root'), so the schema fully documents the parameter. The description adds no additional meaning beyond what the schema provides, resulting in a baseline score of 3.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Check for outdated packages' states the verb ('Check') and resource ('outdated packages'), providing a basic purpose. However, it lacks specificity about scope (e.g., all packages vs. specific ones) and doesn't differentiate from sibling tools like 'suggest_dependency_updates' or 'analyze_dependencies', making it vague in context.

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?

No guidance is provided on when to use this tool versus alternatives such as 'suggest_dependency_updates' or 'analyze_dependencies'. The description offers no context, prerequisites, or exclusions, leaving the agent without usage direction.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/code-alchemist01/development-tools-mcp-Server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server