Skip to main content
Glama
Sign In
aimasteracc

tree-sitter-analyzer

by aimasteracc
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

nav

Read-onlyIdempotent

Trace call paths, callers/callees, impact, lineage, and cross-references across code. Resolve symbols and map tests or context for agent-driven analysis.

Instructions

Code-intelligence (codegraph-compatible) navigation facade (multi-hop: search action=uql). Actions: call_path, callee_tree, callees, caller_tree, callers, co_change, context, impact, lineage, navigate, pulse, pulse_batch, resolve, test_map, trace, xref. Pass action=help with target_action for an exact action schema. Cost: action=callers is slow (prefer nav action=context (1-hop, warm)).

Input Schema

NameRequiredDescriptionDefault
modeNoAction sub-mode (e.g. summary|cycles).
limitNoMax results.
queryNoSearch query/pattern.
scopeNoAction discriminator (e.g. point|graph).
actionYesWhich business capability to invoke, or help for discovery. One of: call_path, callee_tree, callees, caller_tree, callers, co_change, context, help, impact, lineage, navigate, pulse, pulse_batch, resolve, test_map, trace, xref
symbolNoSymbol/function name.
languageNoLanguage hint (usually auto).
file_pathNoTarget file path.
access_modeNoUse only a certified existing index snapshot.
snapshot_idNoOwner-issued certified index snapshot ID.
function_nameNoFunction name (alias of symbol).
output_formatNoOutput format: JSON.
target_actionNoBusiness action to describe when action is help.
source_generationNoOwner-issued certified source generation.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv2.2.0
    • changedInput schema / properties / action / description
      Previous value: -"Which capability to invoke. One of: call_path, callee_tree, callees, caller_tree, callers, co_change, context, impact, lineage, navigate, pulse, pulse_batch, resolve, test_map, trace, xref"New value: +"Which business capability to invoke, or help for discovery. One of: call_path, callee_tree, callees, caller_tree, callers, co_change, context, help, impact, lineage, navigate, pulse, pulse_batch, resolve, test_map, trace, xref"
    • changedInput schema / properties / action / enum
      Previous value: -[
-  "call_path",
-  "callee_tree",
-  "callees",
-  "caller_tree",
-  "callers",
-  "co_change",
-  "context",
-  "impact",
-  "lineage",
-  "navigate",
-  "pulse",
-  "pulse_batch",
-  "resolve",
-  "test_map",
-  "trace",
-  "xref"
-]New value: +[
+  "call_path",
+  "callee_tree",
+  "callees",
+  "caller_tree",
+  "callers",
+  "co_change",
+  "context",
+  "help",
+  "impact",
+  "lineage",
+  "navigate",
+  "pulse",
+  "pulse_batch",
+  "resolve",
+  "test_map",
+  "trace",
+  "xref"
+]
    • addedInput schema / properties / target_action
      Added value: +{
+  "description": "Business action to describe when action is help.",
+  "type": "string"
+}
  2. Changed7 schema fields changedv1.30.0
    • addedInput schema / properties / access_mode
      Added value: +{
+  "description": "Use only a certified existing index snapshot.",
+  "enum": [
+    "read_existing"
+  ],
+  "type": "string"
+}
    • changedInput schema / properties / action / description
      Previous value: -"Which capability to invoke. One of: call_path, callee_tree, callees, caller_tree, callers, co_change, context, impact, lineage, navigate, resolve, test_map, trace, xref"New value: +"Which capability to invoke. One of: call_path, callee_tree, callees, caller_tree, callers, co_change, context, impact, lineage, navigate, pulse, pulse_batch, resolve, test_map, trace, xref"
    • changedInput schema / properties / action / enum
      Previous value: -[
-  "call_path",
-  "callee_tree",
-  "callees",
-  "caller_tree",
-  "callers",
-  "co_change",
-  "context",
-  "impact",
-  "lineage",
-  "navigate",
-  "resolve",
-  "test_map",
-  "trace",
-  "xref"
-]New value: +[
+  "call_path",
+  "callee_tree",
+  "callees",
+  "caller_tree",
+  "callers",
+  "co_change",
+  "context",
+  "impact",
+  "lineage",
+  "navigate",
+  "pulse",
+  "pulse_batch",
+  "resolve",
+  "test_map",
+  "trace",
+  "xref"
+]
    • changedInput schema / properties / output_format / description
      Previous value: -"Output format (toon|json)."New value: +"Output format: JSON."
    • addedInput schema / properties / output_format / enum
      Added value: +[
+  "json"
+]
    • addedInput schema / properties / snapshot_id
      Added value: +{
+  "description": "Owner-issued certified index snapshot ID.",
+  "type": "string"
+}
    • addedInput schema / properties / source_generation
      Added value: +{
+  "description": "Owner-issued certified source generation.",
+  "type": "string"
+}
  3. First observedv1.23.0

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already establish read-only, idempotent, non-destructive, closed-world behavior. The description adds meaningful behavioral context by noting multi-hop support, the help discovery path, and performance characteristics such as `callers` being slow and `context` being a 1-hop warm alternative.

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?

The description is front-loaded and dense, covering purpose, actions, help discovery, and cost in a short space. The long action list duplicates the schema enum, but it helps an agent scan capabilities quickly.

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

Completeness3/5

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

For a 14-parameter facade with no output schema, the description gives only high-level discovery guidance and one cost note. The `help` route mitigates this, but important details such as snapshot/access mode requirements and per-action semantics are left to schema/help rather than the description.

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 description coverage is 100%, so the schema already documents the 14 parameters well. The description references `action`, `target_action`, and a couple of action-specific alternatives, but adds little parameter semantics beyond what the schema provides.

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 clearly identifies the tool as a code-intelligence navigation facade and lists the supported actions, so an agent knows it is a multi-action codegraph query tool. It does not explicitly contrast itself with siblings like search or structure, so it stops short of a 5.

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

Usage Guidelines3/5

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

It gives useful routing guidance for help (`action=help` with `target_action`) and one concrete alternative (`callers` is slow; prefer `context`), but it does not explain when to use nav versus sibling tools or which action fits which scenario beyond the action names.

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

Deploy Server

Other Tools