Skip to main content
Glama
aimasteracc

tree-sitter-analyzer

by aimasteracc
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

viz

Read-onlyIdempotent

Visualize code structure as graphs and UML, explore related symbols, and detect similar functions to analyze codebases locally.

Instructions

Code-intelligence (codegraph-compatible) visualization and similarity facade. Actions: graph, knowledge, similarity, uml. 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: graph, help, knowledge, similarity, uml
symbolNoSymbol/function name.
languageNoLanguage hint (usually auto).
file_pathNoTarget file path.
min_linesNoaction=similarity: min function body lines to consider (default: 5).
max_groupsNoaction=similarity: max clone groups to return (default: 20).
path_filterNoaction=similarity: project-relative path glob filter.
function_nameNoFunction name (alias of symbol).
output_formatNoOutput format: JSON.
target_actionNoBusiness action to describe when action is help.
min_group_sizeNoaction=similarity: min clone group size to report (default: 2).

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: graph, knowledge, similarity, uml"New value: +"Which business capability to invoke, or help for discovery. One of: graph, help, knowledge, similarity, uml"
    • changedInput schema / properties / action / enum
      Previous value: -[
-  "graph",
-  "knowledge",
-  "similarity",
-  "uml"
-]New value: +[
+  "graph",
+  "help",
+  "knowledge",
+  "similarity",
+  "uml"
+]
    • addedInput schema / properties / target_action
      Added value: +{
+  "description": "Business action to describe when action is help.",
+  "type": "string"
+}
  2. Changed2 schema fields changedv1.30.0
    • 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"
+]
  3. Changed3 schema fields changedv1.29.1
    • changedInput schema / properties / action / description
      Previous value: -"Which capability to invoke. One of: graph, similarity, uml"New value: +"Which capability to invoke. One of: graph, knowledge, similarity, uml"
    • changedInput schema / properties / action / enum
      Previous value: -[
-  "graph",
-  "similarity",
-  "uml"
-]New value: +[
+  "graph",
+  "knowledge",
+  "similarity",
+  "uml"
+]
    • addedInput schema / properties / path_filter
      Added value: +{
+  "description": "action=similarity: project-relative path glob filter.",
+  "type": "string"
+}
  4. Changed3 schema fields changedv1.25.0
    • addedInput schema / properties / max_groups
      Added value: +{
+  "description": "action=similarity: max clone groups to return (default: 20).",
+  "type": "integer"
+}
    • addedInput schema / properties / min_group_size
      Added value: +{
+  "description": "action=similarity: min clone group size to report (default: 2).",
+  "type": "integer"
+}
    • addedInput schema / properties / min_lines
      Added value: +{
+  "description": "action=similarity: min function body lines to consider (default: 5).",
+  "type": "integer"
+}
  5. First observedv1.23.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already label the tool readOnly, idempotent, and non-destructive, so the safety profile is covered. The description adds that it is a facade and that help can be requested per action, which is useful, but it discloses little else about behavior such as output structure or action-specific effects.

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 with no filler: the first establishes domain and actions, the second points to self-discovery. Information is front-loaded and every sentence earns its place.

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?

The tool has 15 parameters, 5 actions, and no output schema, yet the description leaves the semantics of each action undefined. The help pointer is useful but shifts the burden onto a preliminary help call; for such a high-complexity tool, more context about action behavior and result types is needed.

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 carries the parameter documentation burden. The description adds only the cross-parameter hint that target_action is used when action is help, which the schema already states. No additional meaning beyond the schema is provided.

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 ... visualization and similarity facade' and enumerates its actions: graph, knowledge, similarity, uml. It is specific enough to convey that this is a dispatcher for code analysis, but it does not distinguish itself from siblings like search or structure beyond the facade framing.

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 only usage guidance is 'Pass action=help with target_action for an exact action schema,' which is a discovery instruction rather than guidance on when to use this tool versus alternatives. No conditional context, exclusions, or sibling routing is provided.

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