Skip to main content
Glama
aimasteracc

tree-sitter-analyzer

by aimasteracc
OverviewSchemaRelated ServersScoreDiscussions
Python
Local

index

Manage your project's code index: check health, trigger full or incremental rebuilds, configure auto-indexing, and query cached AST data for symbols and references.

Instructions

Code-intelligence (codegraph-compatible) index lifecycle hub. Covers codegraph_status, codegraph_full_index, codegraph_autoindex, codegraph_incremental_sync, AST cache query, and whole-project knowledge graph materialization in one tool. Pick a capability via action:

READ-ONLY:

  • action=status — check codegraph index health without writing (codegraph_status equivalent). Returns node/edge counts, staleness, and error indicators. Params: (none).

  • action=cache — query the raw AST cache for symbols, types, and references (read-only modes: search, lookup, stats, changes, watch_status). NOTE: this action ALSO exposes mutating cache modes via mode — index, sync, invalidate, watch_start, watch_stop (and force=true to force a reindex). Params: mode (default search/stats), query, file_path, kind, limit, force.

WRITES ON-DISK INDEX:

  • action=build — full (re)build of the project index. Slow; use when index is absent or corrupt. Params: force.

  • action=full — force a complete full reindex (codegraph_full_index equivalent). Params: (none).

  • action=auto — enable/configure background auto-indexing (codegraph_autoindex equivalent). Params: enable, watch.

  • action=sync — run one incremental sync pass (fast; use after editing files, codegraph_incremental_sync equivalent). Params: paths.

  • action=knowledge — build/update/status for the code+docs knowledge graph sidecar and optional LadybugDB mirror. Params: mode, backend, max_files, max_nodes, max_edges, include_docs.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
modeNoAction sub-mode (e.g. summary|cycles).
limitNoMax results.
queryNoSearch query/pattern.
scopeNoAction discriminator (e.g. point|graph).
actionYesWhich capability to invoke. One of: auto, build, cache, full, knowledge, status, sync
symbolNoSymbol/function name.
languageNoLanguage hint (usually auto).
file_pathNoTarget file path.
function_nameNoFunction name (alias of symbol).
output_formatNoOutput format (toon|json).

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed2 schema fields changedv1.29.1
    • changedInput schema / properties / action / description
      Previous value: -"Which capability to invoke. One of: auto, build, cache, full, status, sync"New value: +"Which capability to invoke. One of: auto, build, cache, full, knowledge, status, sync"
    • changedInput schema / properties / action / enum
      Previous value: -[
-  "auto",
-  "build",
-  "cache",
-  "full",
-  "status",
-  "sync"
-]New value: +[
+  "auto",
+  "build",
+  "cache",
+  "full",
+  "knowledge",
+  "status",
+  "sync"
+]
  2. First observedv1.23.0

TDQS

A4.3/5.0
Behavior5/5

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

Annotations are all false and provide no detail, so the description carries the full burden. It does this exceptionally well by separating READ-ONLY operations from 'WRITES ON-DISK INDEX' operations, disclosing that cache also exposes mutating modes, mentioning force reindexing, invalidate, and background auto-indexing, and flagging slow vs fast operations. No contradiction with annotations exists.

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?

Although long, the description is appropriately sized for a multi-action hub and is well structured with READ-ONLY and WRITES sections, bullets, and inline parameter lists. It front-loads the core concept and every section earns its place.

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?

Given the tool's complexity, seven actions, ten parameters, and no output schema, the description covers action selection, side effects, performance characteristics, and status return information well. It does not describe return shapes for most actions or error behavior, and some schema parameters are not mentioned, leaving minor gaps.

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?

Schema coverage is 100% so the baseline is 3, but the description adds real value by mapping parameters per action, stating defaults like mode (default search/stats), and naming additional params absent from the schema such as kind, enable, watch, paths, backend, max_files, max_edges, and include_docs. Some schema params like scope, symbol, language, and output_format are left unmapped, preventing a perfect score.

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 a code-intelligence index lifecycle hub and enumerates seven distinct capabilities via the action parameter, with concrete verbs like check, query, build, sync, and materialize. It does not explicitly differentiate from sibling tools such as search, nav, or health, so it misses the top score.

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?

The description gives strong in-tool routing guidance, such as 'use when index is absent or corrupt' for build, 'fast; use after editing files' for sync, and explicit read-only vs mutating modes for cache. It lacks explicit when-not-to-use guidance against sibling tools, but within the tool the action selection conditions are clear.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/aimasteracc/tree-sitter-analyzer'

If you have feedback or need assistance with the MCP directory API, please join our Discord server