Skip to main content
Glama

Project overview

droidmap_report
Read-onlyIdempotent

Generate a Markdown project overview covering module dependencies, Room databases, navigation flow and findings, with Mermaid diagrams, to get oriented in an unfamiliar Android codebase.

Instructions

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.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "droidmap_report"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.7/5.0
Behavior5/5

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

Beyond the readOnly/idempotent/closed annotations, it discloses operating behavior: it reads source files, never runs Gradle or the app, and sends nothing anywhere, so the agent knows there are no side effects or external calls. It also warns the returned Markdown can be long on large projects, which matters for context budgeting.

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 the core action, then the content inventory, then usage routing, then behavioral notes. The content enumeration is dense but each item (Room versions, migrations, Mermaid diagrams) tells the agent what it will get, so little is padding; it could still be tightened slightly.

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?

With no output schema, the description carries the return-value burden and does so by naming the format (Markdown) and its potential size. For a zero-argument, read-only overview tool this is nearly complete; only the exact section layout or diagram granularity is left implicit.

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?

The tool takes zero parameters, so the baseline is 4. The description confirms 'Takes no arguments,' which agrees with the empty schema and prevents wasted attempts to pass filters.

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 ('Write a Markdown overview of the whole project') and enumerates the exact contents: summary, modules and dependencies, Room DBs with versions/migrations/coverage, navigation, DI, permissions, findings, plus Mermaid diagrams. This is clearly distinguishable from siblings like droidmap_find or droidmap_show, which target one part.

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?

Explicit when-to-use ('use it once to get oriented in an unfamiliar project') and explicit alternatives ('use droidmap_find, droidmap_show or droidmap_impact for one part'). The selection condition between the broad overview and the narrow lookups is stated outright.

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