Skip to main content
Glama

Show one node

droidmap_show
Read-onlyIdempotent

Inspect one graph node to see its kind, file:line, attributes, and direct dependencies and dependents with edge kinds; use it to examine a class, entity, route, or module closely.

Instructions

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.

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_show"
  }
}

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.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.1.1
    • 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 read-only, closed-world and idempotent, but the description adds substantive behavior the agent could not otherwise know: it reads source files, never runs Gradle or the app, and transmits nothing. It also states the return medium ('plain text') and the direct-vs-transitive scope of the result, which shapes how the output should be interpreted.

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 and return payload, then alternatives, then execution guarantees. Information density is high and each clause earns its place, though the single run-on paragraph of parenthetical examples slightly taxes readability.

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 carries the burden of explaining return content and does so precisely (kind, file:line, attributes, inbound and outbound edges with edge kinds, plain text). For a one-parameter read tool, nothing material 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 coverage is 100% and the schema parameter description already covers accepted id/name/partial-name forms and the multi-match failure behavior in detail. The description adds only indirect guidance ('use droidmap_find when you do not know its name'), so baseline 3 applies when the schema does the heavy lifting.

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 ('Show one node of the graph') and enumerates exactly what is returned: kind, file:line, attributes, direct dependencies and direct users with edge kinds. It explicitly distinguishes itself from droidmap_impact (transitive dependents) and droidmap_find (unknown name), so an agent can route correctly without opening any schema.

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 a positive use case ('look closely at one class, entity, route or module') and names two alternatives with the conditions that select them: droidmap_impact for transitive dependents, droidmap_find when the name is unknown. Nothing is left to inference.

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