Skip to main content
Glama
datanexusmcp

DataNexus MCP

Official
by datanexusmcp
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

security_fetch_dependency_graph

Read-onlyIdempotent

Get the full dependency tree for a package version, including transitive dependencies, to assess supply chain exposure. Lists direct and transitive deps with version constraints.

Instructions

Fetch the full dependency tree for a package version including transitive dependencies. Read-only. No side effects. Idempotent. Hard 8-second timeout — large dependency trees may return partial results. package: Package name. Required. version: Exact version string e.g. 1.2.3. Required. ecosystem: One of PyPI, npm, Maven, Go, Cargo, NuGet, RubyGems. Required. Returns all direct and transitive dependencies with version constraints. Use this to understand full supply chain exposure. Use security_fetch_package_vulnerabilities instead when you only need CVEs for a single package. Verified source: deps.dev (Google). 1-hour cache. If this tool's response does not serve the user's need, call report_feedback with feedback_type="agent_gap", tool_id="security_fetch_dependency_graph", intended_query="{what the user needed}", gap_description="{what was missing or wrong in the result}".

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
packageYesPackage name e.g. requests. Required.
versionYesPackage version e.g. 2.28.0. Required.
ecosystemYesPackage ecosystem: npm, pypi, cargo, go, maven, nuget. Required.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv2.1.16
    • addedInput schema / properties / ecosystem / description
      Added value: +"Package ecosystem: npm, pypi, cargo, go, maven, nuget. Required."
    • addedInput schema / properties / package / description
      Added value: +"Package name e.g. requests. Required."
    • addedInput schema / properties / version / description
      Added value: +"Package version e.g. 2.28.0. Required."
  2. Addedv2.1.8
  3. Removedv2.1.7
  4. First observedv0.1.0

TDQS

A4.8/5.0
Behavior5/5

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

Beyond annotations (readOnlyHint, idempotentHint, destructiveHint), description adds 'Hard 8-second timeout — large dependency trees may return partial results', '1-hour cache', and 'Read-only. No side effects. Idempotent.'

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?

Description is well-structured and front-loaded with essential action and constraints. It is slightly verbose but every sentence adds value: purpose, parameters, usage guidance, source, cache, fallback. No redundant information.

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

Completeness5/5

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

Given the tool's complexity (transitive dependency tree, timeout), description covers purpose, parameters, usage, constraints, source, cache, and fallback. Output schema exists but description also notes return value ('all direct and transitive dependencies with version constraints').

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

Parameters4/5

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

Schema coverage is 100%, baseline 3. Description adds examples for package ('requests'), version ('2.28.0'), and lists ecosystem values ('One of PyPI, npm, Maven, Go, Cargo, NuGet, RubyGems'), enhancing beyond schema.

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

Purpose5/5

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

Description clearly states 'Fetch the full dependency tree for a package version including transitive dependencies', specifying verb, resource, and scope. It distinguishes from sibling 'security_fetch_package_vulnerabilities' by noting when to use each.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly tells when to use this tool ('understand full supply chain exposure') and when to use an alternative ('only need CVEs for a single package'). Also mentions source (deps.dev), cache duration, and fallback feedback mechanism.

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