Skip to main content
Glama

rdeps

Read-onlyIdempotent

Trace the reverse dependency tree of a module to see which files and modules depend on it, hop by hop, so you can judge the blast radius of a change before editing.

Instructions

Reverse dependency tree of a module: who uses it, 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": "rdeps"
  }
}

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

B3.1/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint=false and destructiveHint=false, so safety and repeatability are covered. The description adds essentially nothing beyond structured data – it does not mention the 200-item cap behavior, the effect of depth=0, or whether the traversal crosses package/file boundaries, and 'hop by hop' merely restates the depth parameter.

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 compact sentence with the core concept front-loaded and a clarifying gloss appended. No filler, no repetition.

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 tool is simple (3 flat parameters, no output schema), and the schema is fully documented, so the description is minimally sufficient. It nevertheless leaves out traversal semantics an agent would want – what truncated results look like at the 200-item threshold and how cycles or depth=0 are handled.

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 all three parameters (module, depth, all) are already documented with defaults, bounds, and an example module path. The description adds no meaning beyond the schema, which is the correct baseline of 3 when the schema carries the full burden.

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 operation and resource: 'Reverse dependency tree of a module', followed by the plain-language gloss 'who uses it, hop by hop'. The word 'reverse' implicitly contrasts with a forward dependency tool (e.g. deps) and clearly separates it from analysis-style siblings, though no sibling is named explicitly.

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 statement of when to choose this over the available alternatives such as impact, usages, or deps, nor any stated preconditions. An agent must infer from the phrase 'who uses it' that this is a transitive dependents query rather than a single-level usage lookup.

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