Skip to main content
Glama

arch_archaeologist

Scans a codebase AST to map module dependency graphs and detect uncalled zombie or dead functions, so you can locate unused code for cleanup.

Instructions

Scans codebase AST to map module dependency graphs and detect uncalled zombie/dead functions.

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": {
      "dir_path": "<dir_path>"
    },
    "name": "arch_archaeologist"
  }
}

Input Schema

NameRequiredDescriptionDefault
dir_pathYesPath to directory to analyze

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden. It states that the tool scans and analyzes code, but omits whether it is read-only, whether it modifies files, what scale it supports, and what it returns.

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 definition is a single front-loaded sentence with no filler. Both capabilities, dependency mapping and dead-function detection, are expressed efficiently.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema and no annotations, the description should explain the return shape, safety profile, and limitations. It does not, leaving an agent unsure what the analysis produces or whether invoking it has side effects.

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 only parameter, dir_path, is already fully described in the schema as the directory to analyze. The description adds no further constraints, path-format details, or semantic nuance beyond that.

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?

The description gives specific verbs and resources: scanning an AST, mapping module dependency graphs, and detecting uncalled dead functions. It is clear what the tool does, though it does not explicitly distinguish itself from any alternative analysis tools.

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

Usage Guidelines2/5

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

The description provides no explicit when-to-use guidance, prerequisites, exclusions, or alternatives. Usage is only implied by the stated purpose.

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