Skip to main content
Glama

What depends on this

droidmap_impact
Read-onlyIdempotent

Lists every transitive dependent of a code node—classes, DAOs, databases, screens, routes, ViewModels, bindings, modules, and tests—so you know what to update and test before changing it.

Instructions

List everything that depends on one node, transitively: who injects a class, which DAOs and databases use an entity, which screens use a ViewModel, which functions navigate to a destination, which modules depend on a module, and the test classes whose calls reach it. Use it before changing a class, entity, route, ViewModel, binding or module, to know what else to update and test; use droidmap_show for only the direct links in both directions, and droidmap_diff once the change is made. Read-only and local: it reads the source files, never runs Gradle or the app, and sends nothing anywhere. Returns plain text: the node and its file, then up to 200 dependents nearest first, each with its depth, kind, the edge it depends through and file:line, then the tests and modules affected; or "Nothing in the graph depends on it."

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

Input Schema

NameRequiredDescriptionDefault
nodeYesThe node: its id as droidmap_find prints it, its name, or part of a name, such as 'TopicEntity', ':core:data', 'editor?id={id}' or 'AppDatabase'. When several nodes match, the call fails and lists their ids: call again with one of them.
depthNoHow many dependency steps to follow outwards: 1 lists only direct users; the default, 4, is enough for most changes.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.1.1
    • addedInput schema / properties / depth / description
      Added value: +"How many dependency steps to follow outwards: 1 lists only direct users; the default, 4, is enough for most changes."
    • changedInput schema / properties / node / description
      Previous value: -"Node id, name or part of a name (e.g. 'TopicEntity', ':core:data', 'editor?id={id}', 'AppDatabase')."New value: +"The node: its id as droidmap_find prints it, its name, or part of a name, such as 'TopicEntity', ':core:data', 'editor?id={id}' or 'AppDatabase'. When several nodes match, the call fails and lists their ids: call again with one of them."
  2. First observedv0.1.0

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive/closed-world, and the description still adds substantive behavior: it reads source files, never runs Gradle or the app, sends nothing anywhere, caps results at 200 dependents ordered nearest-first with depth/kind/edge/file:line, and names the empty-result string.

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?

Front-loaded with purpose, then when-to-use, then behavior, then return format — a sensible order with no filler. The opening sentence is long because it enumerates node kinds, but each clause maps to a real dependent category rather than restating the title.

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?

With no output schema, the description fully specifies the return shape (node and file, then dependents with depth/kind/edge/file:line, then tests and modules) plus the empty case. Combined with 100% schema coverage on both parameters, nothing needed to call this 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%, including the disambiguation behavior for ambiguous node matches and the depth default/max, so the schema already carries parameter meaning. The description adds only the notion of transitive reach, which is already implied by the depth parameter's own documentation, so baseline 3 applies.

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?

States a specific verb and resource ('List everything that depends on one node, transitively') and then enumerates concrete dependent kinds (injected classes, DAOs/databases, screens, navigation destinations, modules, test classes), so an agent knows exactly what comes back. It is clearly separable from droidmap_show (direct links, both directions) and droidmap_diff (post-change).

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?

Gives an explicit trigger ('Use it before changing a class, entity, route, ViewModel, binding or module, to know what else to update and test') and names both alternatives with the condition that selects them: droidmap_show for direct links only, droidmap_diff after the change is made.

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