Skip to main content
Glama

Find nodes by name

droidmap_find
Read-onlyIdempotent

Search Android project graph nodes by id or name to find exact module, Room entity, DAO, route, screen, ViewModel, or Hilt/Koin binding names needed for impact and show queries.

Instructions

Search the graph's nodes by id or name: modules, Room databases, entities, DAOs and migrations, navigation destinations and routes, screens, ViewModels, injectable classes, Hilt and Koin modules and bindings, components and permissions. Case is ignored; an exact name ranks first, then a name that starts with the text, then one that contains it. Use it to get the exact name or id that droidmap_impact and droidmap_show need when you know only part of it. Read-only and local: it reads the source files, never runs Gradle or the app, and sends nothing anywhere. Returns plain text, one node per line: name, kind and file:line (with the id when names repeat); or "No node matches".

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": {
      "query": "<query>"
    },
    "name": "droidmap_find"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoThe most nodes to list (default 20).
queryYesThe text to look for in node names and ids, such as 'Topic', 'UserDao', ':feature:home' or 'settings'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv0.1.1
    • addedInput schema / properties / limit / description
      Added value: +"The most nodes to list (default 20)."
    • addedInput schema / properties / limit / maximum
      Added value: +200
    • addedInput schema / properties / limit / minimum
      Added value: +1
    • addedInput schema / properties / query / description
      Added value: +"The text to look for in node names and ids, such as 'Topic', 'UserDao', ':feature:home' or 'settings'."
  2. First observedv0.1.0

TDQS

A4.9/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 real context beyond them: it reads source files, never runs Gradle or the app, sends nothing anywhere, and explains result ranking (exact, then prefix, then substring) plus the plain-text line format and the no-match string. That is substantive behavioral disclosure an agent cannot get from the annotations.

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?

The description is dense but front-loaded: search scope first, then matching rules, then the routing guidance to siblings, then the safety note, then the return format. Every sentence carries distinct information and nothing is padded or repeated.

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?

Even though there is no output schema, the description describes the return value precisely (one node per line: name, kind, file:line, id when names repeat, or "No node matches"). Combined with the ranking rules and local read-only behavior, an agent has everything needed for this two-parameter search tool.

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%, so the baseline is 3; the description goes further by clarifying matching semantics the schema omits — that case is ignored and that results are ordered exact, then starts-with, then contains, which directly affects how 'query' should be chosen and how results should be read. It says nothing extra about 'limit' beyond the schema default, which keeps it from a 5.

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?

The description gives a specific verb and resource ("Search the graph's nodes by id or name") and enumerates the node kinds covered — modules, Room databases, entities, DAOs, migrations, navigation destinations, screens, ViewModels, injectables, Hilt/Koin modules, components, permissions. That enumeration makes it instantly distinguishable from siblings like droidmap_impact or droidmap_show, which it also names.

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?

It states the exact usage condition: use this "to get the exact name or id that droidmap_impact and droidmap_show need when you know only part of it." This is an explicit when-to-use plus a handoff to the two alternatives that consume its output, leaving little to inference.

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