Skip to main content
Glama
Sign In
DepShield MCP

DepShield MCP

by devanshkaria88
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

find_safe_version

Find the newest version of npm or PyPI packages with zero known vulnerabilities. Checks CVE databases to recommend secure alternatives and prevent installing compromised dependencies.

Instructions

Find the newest version of a package with zero known vulnerabilities.

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

Input Schema

NameRequiredDescriptionDefault
nameYesPackage name
ecosystemNoPackage ecosystem. Defaults to npm.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
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. While it specifies the selection criteria (newest version with zero vulnerabilities), it fails to disclose error handling (what happens when no safe version exists), return format, or the vulnerability database source.

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, front-loaded sentence of 11 words with zero redundancy. Every word contributes essential information about the tool's function.

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?

Given the simple two-parameter input schema with complete coverage, the description is minimally adequate. However, lacking both annotations and an output schema, it should ideally disclose error states (e.g., package not found, no safe version available) to be complete.

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 100% with both parameters fully documented. The description maps the concept of 'package' to the 'name' parameter but does not add semantics beyond the schema, such as explaining the ecosystem default behavior or valid values.

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 clearly states the specific action (find), resource (package version), and constraint (zero known vulnerabilities). However, it does not explicitly differentiate from siblings like check_dependency or suggest_alternative that also handle security concerns.

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 description provides no guidance on when to use this tool versus alternatives like check_dependency or suggest_alternative. It omits prerequisites (e.g., exact package name requirements) and does not indicate when no safe version exists.

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