Skip to main content
Glama
aimasteracc

tree-sitter-analyzer

by aimasteracc
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

project

Analyze codebases and retrieve project intelligence through overview, metrics, parser, skills, and workflow actions. Pass action=help with target_action to discover exact schemas for each capability.

Instructions

Code-intelligence (codegraph-compatible) project-intelligence hub. Actions: card, doc_sync, journal, metrics, overview, parser, skills, smart, workflow. Pass action=help with target_action for an exact action schema.

Input Schema

TableJSON 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: card, doc_sync, help, journal, metrics, overview, parser, skills, smart, workflow
symbolNoSymbol/function name.
languageNoLanguage hint (usually auto).
file_pathNoTarget file path.
function_nameNoFunction name (alias of symbol).
output_formatNoOutput format: JSON.
target_actionNoBusiness action to describe when action is help.

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: card, doc_sync, journal, metrics, overview, parser, skills, smart, workflow"New value: +"Which business capability to invoke, or help for discovery. One of: card, doc_sync, help, journal, metrics, overview, parser, skills, smart, workflow"
    • changedInput schema / properties / action / enum
      Previous value: -[
-  "card",
-  "doc_sync",
-  "journal",
-  "metrics",
-  "overview",
-  "parser",
-  "skills",
-  "smart",
-  "workflow"
-]New value: +[
+  "card",
+  "doc_sync",
+  "help",
+  "journal",
+  "metrics",
+  "overview",
+  "parser",
+  "skills",
+  "smart",
+  "workflow"
+]
    • addedInput schema / properties / target_action
      Added value: +{
+  "description": "Business action to describe when action is help.",
+  "type": "string"
+}
  2. Changed2 schema fields changedv2.0.0
    • changedInput schema / properties / action / description
      Previous value: -"Which capability to invoke. One of: card, doc_sync, files, journal, metrics, overview, parser, skills, smart, tools, workflow"New value: +"Which capability to invoke. One of: card, doc_sync, journal, metrics, overview, parser, skills, smart, workflow"
    • changedInput schema / properties / action / enum
      Previous value: -[
-  "card",
-  "doc_sync",
-  "files",
-  "journal",
-  "metrics",
-  "overview",
-  "parser",
-  "skills",
-  "smart",
-  "tools",
-  "workflow"
-]New value: +[
+  "card",
+  "doc_sync",
+  "journal",
+  "metrics",
+  "overview",
+  "parser",
+  "skills",
+  "smart",
+  "workflow"
+]
  3. Changed4 schema fields changedv1.30.0
    • changedInput schema / properties / action / description
      Previous value: -"Which capability to invoke. One of: doc_sync, files, journal, metrics, overview, parser, skills, smart, tools, workflow"New value: +"Which capability to invoke. One of: card, doc_sync, files, journal, metrics, overview, parser, skills, smart, tools, workflow"
    • changedInput schema / properties / action / enum
      Previous value: -[
-  "doc_sync",
-  "files",
-  "journal",
-  "metrics",
-  "overview",
-  "parser",
-  "skills",
-  "smart",
-  "tools",
-  "workflow"
-]New value: +[
+  "card",
+  "doc_sync",
+  "files",
+  "journal",
+  "metrics",
+  "overview",
+  "parser",
+  "skills",
+  "smart",
+  "tools",
+  "workflow"
+]
    • 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"
+]
  4. First observedv1.23.0

TDQS

C2.7/5.0
Behavior2/5

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

Annotations are all false and provide no safety profile, so the description carries the burden. It lists actions and a help mechanism, but discloses no side effects, mutability, output shape, permissions, or per-action behavior for a multi-action tool.

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?

Two crisp sentences, front-loaded with the hub role and an actionable discovery instruction; no filler. The action list is dense but necessary given the tool's design.

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 high-complexity 10-action tool with no output schema, the description relies on the action=help escape hatch rather than documenting behaviors. This makes it minimally usable but incomplete for selecting the right action without an extra help call.

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%, so the baseline is 3. The description adds only the hint that target_action is used with action=help, which the schema already states; it adds no extra meaning to the 11 parameters.

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

Purpose3/5

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

The description identifies the tool as a 'project-intelligence hub' and enumerates ten action names, but it never states a concrete verb+resource or what the tool actually accomplishes. It is distinguishable from siblings only by the action names, not by an explicit statement of purpose.

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?

No guidance is given on when to invoke this hub versus sibling tools like search, edit, or index. The only directive, 'Pass action=help with target_action', explains schema discovery, not usage conditions or alternatives.

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