Skip to main content
Glama

deps_check

Read-only

Check package.json, requirements.txt, pyproject.toml, or Cargo.toml dependencies against registries to find outdated major/minor/patch versions and deprecated packages.

Instructions

Check all deps of package.json/requirements.txt/pyproject.toml/Cargo.toml vs registries: major/minor/patch behind, deprecated.

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": "deps_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathNomanifest or folder
include_devNo
only_outdatedNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.2

TDQS

B3/5.0
Behavior3/5

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

The readOnlyHint annotation already establishes this is a safe read operation, so the description does not need to argue safety. It does add useful behavior beyond annotations by disclosing that it queries external registries and classifies drift by semver level plus deprecation. It omits network/rate-limit or offline behavior and how results are ordered or truncated.

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?

A single compact sentence with the resource and the reported findings front-loaded and no filler. It is telegraphic (colon-list style) but every element carries information. Slight cost in readability from the dense slash-separated file list.

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 no output schema, the description does reasonably well by naming the findings returned (semver drift level, deprecation). However, for a 3-parameter tool with 33% schema coverage it leaves two flags completely unexplained and says nothing about how results are presented. An agent can call it with a path, but cannot confidently use include_dev or only_outdated.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 33%: 'path' is described in the schema as 'manifest or folder', but 'include_dev' and 'only_outdated' carry no description anywhere. The description never mentions any of the three parameters, so it does not compensate for the low coverage. The only implicit link is that the named manifest types clarify what 'path' should point at.

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 ('Check') and resource ('all deps of package.json/requirements.txt/pyproject.toml/Cargo.toml') plus the comparison target (registries) and the findings it produces (major/minor/patch behind, deprecated). An agent can tell this is a dependency-audit tool rather than a generic package lookup like package_info. It stops short of explicitly naming or contrasting a sibling.

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 explicit when-to-use or when-not-to-use statement and no named alternative. Usage is only inferable from the subject matter (auditing manifests for outdated/deprecated deps). Nothing tells the agent whether to prefer this over package_info or what prerequisite (e.g., a resolvable manifest path) is required.

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