Skip to main content
Glama

get_architecture_graph

Returns a project's top architectural God Nodes and dependency topology in under 250 tokens without file crawling, helping AI agents see code structure before reading or searching files.

Instructions

Returns top architectural God Nodes and dependency topology for the target project in < 250 tokens without file crawling. Call this BEFORE reading files or searching.

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": "get_architecture_graph"
  }
}

Input Schema

NameRequiredDescriptionDefault
project_pathNoOptional root path of the project (defaults to active workspace, or pass '.' or absolute path)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.8.4

TDQS

A3.8/5.0
Behavior3/5

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

With no annotations, the description carries the whole burden. It usefully discloses two behavioral traits: output is bounded to '< 250 tokens' and it works 'without file crawling', which tells the agent about cost and side effects. It does not state that it is strictly read-only, nor what happens on an invalid/missing project_path.

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?

Two sentences, front-loaded with the resource and payoff, then the invocation rule. No filler or restated title.

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?

For a one-optional-param tool with no output schema, the description covers what comes back, its size bound, and when to call it. The only real gap is that the returned structure ('God Nodes', 'topology') is never characterized, leaving the agent to interpret output format on its own.

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?

The single project_path parameter is fully described in the schema (100% coverage), including the default-to-active-workspace behavior and accepted '.' or absolute paths. The description adds no meaning beyond that, so baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource: 'Returns top architectural God Nodes and dependency topology for the target project'. An agent knows it is a project-level architecture summarizer. The jargon 'God Nodes' is undefined, and the sibling set (list_dir, smart_read_file, scoped_search) is only implicitly contrasted rather than named.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

'Call this BEFORE reading files or searching' gives explicit ordering guidance that positions it ahead of the read/search siblings. It lacks an explicit when-not or a named alternative for cases where the graph is insufficient, but the sequencing intent is unambiguous.

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