Skip to main content
Glama

BRAINIAC Cybersecurity Intelligence

Get dependency tree

cybersecurity-intelligence_dependency-tree

Return direct and transitive dependencies, dependency versions and available dependency metadata using Google deps.dev API. Price $0.05 USDC. POST /api/v1/cybersecurity-intelligence/dependency-tree. Unpaid calls return 402 and do not run.

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": {
      "ecosystem": "<ecosystem>",
      "packageName": "<packageName>"
    },
    "name": "cybersecurity-intelligence_dependency-tree"
  }
}

Input Schema

NameRequiredDescriptionDefault
versionNo
ecosystemYes
packageNameYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose two genuinely useful behaviors: a per-call price of $0.05 USDC and that unpaid calls fail with 402 without executing. That is real operational context beyond the schema. However, it says nothing about what happens when the optional version is omitted (latest vs. error), response size/depth for large transitive graphs, or rate limits.

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?

Three short sentences with the primary purpose front-loaded, followed by cost and failure-mode facts. No filler or marketing prose. The raw endpoint path is of marginal value to an agent but is compact enough not to detract.

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?

The description does state what comes back (direct and transitive dependencies, versions, metadata), which partly offsets the absence of an output schema. Against a tool with no annotations and a completely undocumented parameter set, though, it leaves the agent guessing about default version resolution and result depth. Adequate but with clear gaps.

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 0% with three parameters, so the description must compensate and does not. It never mentions the optional 'version' parameter at all, leaving its default behavior undefined, and adds no meaning to the ecosystem enum beyond the schema's own value list. Only 'packageName' is weakly implied by the phrase about dependency metadata.

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 names a specific verb and resource ('Return direct and transitive dependencies, dependency versions and available dependency metadata') and identifies the upstream source (Google deps.dev API). It is unambiguous on its own, but it never contrasts itself with the six sibling package-analysis tools, so the agent must infer the distinction from names alone.

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

Usage Guidelines3/5

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

Usage is only implied: an agent can infer this is the tool for enumerating a package's dependency graph given an ecosystem and package name. There is no explicit when-to-use/when-not-to-use guidance and no pointer to a sibling such as lockfile-audit or vulnerability for adjacent questions. The payment precondition ('Price $0.05 USDC… Unpaid calls return 402') is the closest thing to a stated prerequisite.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources