Skip to main content
Glama

deps

Read-onlyIdempotent

Traces a module's outgoing dependency tree hop by hop, showing what it uses so you can inspect dependencies before making changes.

Instructions

Outgoing dependency tree of a module: what it uses, hop by hop.

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

Input Schema

NameRequiredDescriptionDefault
allNoList everything instead of stopping at 200 items.
depthNoHow many hops to follow.
moduleYesModule ID or file path, as printed by other tools (e.g. src/billing/invoice).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.1

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so safety is covered. The description contributes only the "tree / hop by hop" framing; it does not mention the 200-item truncation behavior (left to the schema), ordering, or what happens when the module is unknown. With annotations doing the heavy lifting, this is adequate but thin.

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?

A single front-loaded sentence with zero filler; the head noun identifies the resource and the trailing clause explains traversal semantics. Nothing is redundant or padded.

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

Completeness4/5

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

For a three-parameter read-only traversal tool with complete schema descriptions and full annotation coverage, the description supplies the essential framing. No output schema exists, so a note on return shape would help, but nothing an agent needs to invoke it correctly is missing.

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 description coverage is 100%, so module, depth and all are fully documented in the schema itself. The description's "hop by hop" mildly reinforces the depth parameter but adds no format or syntax detail beyond it. Baseline 3 applies.

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?

"Outgoing dependency tree of a module" names a specific resource and traversal direction, and "what it uses, hop by hop" clarifies the semantics of a dependency walk. The word "Outgoing" implicitly contrasts with the reverse-dependency sibling (rdeps), but no sibling is named, so differentiation requires inference.

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: the agent can infer this answers "what does X depend on" rather than "what depends on X." There is no explicit when-to-use, no mention of alternatives like rdeps/impact/boundaries, and no stated prerequisites (e.g. whether the module must be indexed).

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