Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

droidmap answers Android structure questions from a static graph of this project, rebuilt from the source files when they change. Use droidmap_impact before changing an entity, route, ViewModel, binding or module, and droidmap_check and droidmap_diff after; droidmap_explain says how to fix a finding, and droidmap_find gives the exact name when you know only part of it.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": false
}

Tools

Functions exposed to the LLM to take actions

NameDescription
droidmap_checkA

Run droidmap's rules on the whole project and list what compiles but would crash or lose data at runtime: Room (missing or failing migrations, schema files out of date, untested migration steps), navigation (routes nothing registers, missing arguments, route types without a NavType, deep links no intent filter accepts), Hilt and Koin bindings, WorkManager setup and inputs, manifest components, permissions, Intent extras and notification channels, DataStores and databases built more than once, Gson and Moshi models that R8 renames, and Gradle module rules and cycles. Use it after editing to confirm nothing new broke; use droidmap_diff for what a change touches and droidmap_explain for how to fix a finding. Read-only and local: it reads the source files, never runs Gradle or the app, and sends nothing anywhere. Findings recorded in the project's droidmap-baseline.json are left out, with a note saying how many. Returns plain text: each finding's severity, rule id and file:line, then the problem, and a count by severity at the end; or "No findings."

droidmap_impactA

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."

droidmap_diffA

Map a code change onto the graph: the declarations whose lines changed since a git ref (by default the uncommitted changes, new files included), the ones removed, everything that depends on them (screens, destinations, ViewModels, Room, bindings, modules), the test classes whose calls reach the changed code, and the findings in the changed files, including those only a comparison shows (a shipped Room schema or a stored enum constant changed, a Worker renamed). Use it after editing, to see what else to update and which tests to run; use droidmap_impact before editing. Read-only: it runs git diff and reads the source files, never runs Gradle, and changes nothing; the project must be in a git repository. Returns plain text in sections: Changed, Removed, Affected (grouped by kind), Tests that cover it, and Findings in the changed files.

droidmap_showA

Show one node of the graph: its kind, file:line and attributes (a destination's route and arguments, a database's version, a binding's qualifier), then the nodes it depends on directly and the nodes that use it directly, each with the edge kind and file:line. Use it to look closely at one class, entity, route or module; use droidmap_impact for everything that depends on it transitively, and droidmap_find when you do not know its name. Read-only and local: it reads the source files, never runs Gradle or the app, and sends nothing anywhere. Returns plain text.

droidmap_findA

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".

droidmap_reportA

Write a Markdown overview of the whole project: a summary, the modules and their dependencies, Room databases with their versions, migrations and test coverage, navigation destinations and how screens connect, dependency injection, permissions and the current findings, with Mermaid diagrams of the modules and the screen flow. Use it once to get oriented in an unfamiliar project; use droidmap_find, droidmap_show or droidmap_impact for one part. Read-only and local: it reads the source files, never runs Gradle or the app, and sends nothing anywhere. Takes no arguments. Returns Markdown, which can be long on a large project.

droidmap_explainA

Explain one droidmap rule: what it finds, why it matters (the crash or data loss it prevents) and how to fix what it found, with code examples, and its page online. Use it when droidmap_check or droidmap_diff reports a finding you do not know how to fix. It reads documentation bundled with droidmap, so it needs no project and changes nothing. Returns Markdown.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A4.5/5.0

Scored across 7 tools

Disambiguation5/5

Each tool targets a distinct action on the code graph: check (rule linting), diff (git change mapping), impact (transitive dependents), show (single-node detail), find (node search), report (project overview), explain (rule documentation). Descriptions even include explicit sibling disambiguation cues like 'use droidmap_diff for what a change touches' and 'use droidmap_impact for transitive, droidmap_show for direct links'.

Naming Consistency5/5

Every tool is a single lowercase word appended to a uniform 'droidmap_' namespace prefix, forming a predictable droidmap_<action> pattern. No camelCase mixing or inconsistent verb styles; the naming reads like a coherent family of graph/analysis operations.

Tool Count5/5

Seven tools is well within the ideal 3-15 range and each earns its place with a non-redundant role in a codebase-graph analysis workflow. Nothing feels padded or missing from the set.

Completeness4/5

The surface covers the full exploratory lifecycle: find a node, inspect it, map its dependents, diff changes, lint rules, understand findings, and get a whole-project report. The main minor gap is baseline handling: findings are excluded via droidmap-baseline.json, but no tool exists to create or update that baseline, leaving agents to work around it externally.

Maintenance

ActivityMaintained
ResponsivenessNo recent community issues