Skip to main content
Glama
aimasteracc

tree-sitter-analyzer

by aimasteracc
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

search

Read-onlyIdempotent

Query code symbols, text, semantic relations, and dependency graphs. Execute chain, query, or tql_execute actions to locate code patterns and navigate AST structures.

Instructions

Code-intelligence (codegraph-compatible) search facade. Actions: chain, query, select, semantic, subscribe, symbol, text, tql_execute, tql_schema, unsubscribe. Pass action=help with target_action for an exact action schema.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
kindNoSymbol kind filter for action=symbol (default: any).
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: chain, help, query, select, semantic, subscribe, symbol, text, tql_execute, tql_schema, unsubscribe
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: chain, query, select, semantic, subscribe, symbol, tql_execute, tql_schema, unsubscribe"New value: +"Which business capability to invoke, or help for discovery. One of: chain, help, query, select, semantic, subscribe, symbol, text, tql_execute, tql_schema, unsubscribe"
    • changedInput schema / properties / action / enum
      Previous value: -[
-  "chain",
-  "query",
-  "select",
-  "semantic",
-  "subscribe",
-  "symbol",
-  "tql_execute",
-  "tql_schema",
-  "unsubscribe"
-]New value: +[
+  "chain",
+  "help",
+  "query",
+  "select",
+  "semantic",
+  "subscribe",
+  "symbol",
+  "text",
+  "tql_execute",
+  "tql_schema",
+  "unsubscribe"
+]
    • 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: batch, chain, query, select, semantic, subscribe, symbol, tql_execute, tql_schema, unsubscribe"New value: +"Which capability to invoke. One of: chain, query, select, semantic, subscribe, symbol, tql_execute, tql_schema, unsubscribe"
    • changedInput schema / properties / action / enum
      Previous value: -[
-  "batch",
-  "chain",
-  "query",
-  "select",
-  "semantic",
-  "subscribe",
-  "symbol",
-  "tql_execute",
-  "tql_schema",
-  "unsubscribe"
-]New value: +[
+  "chain",
+  "query",
+  "select",
+  "semantic",
+  "subscribe",
+  "symbol",
+  "tql_execute",
+  "tql_schema",
+  "unsubscribe"
+]
  3. Changed4 schema fields changedv1.30.0
    • changedInput schema / properties / action / description
      Previous value: -"Which capability to invoke. One of: batch, chain, content, grep, query, select, subscribe, symbol, unsubscribe"New value: +"Which capability to invoke. One of: batch, chain, query, select, semantic, subscribe, symbol, tql_execute, tql_schema, unsubscribe"
    • changedInput schema / properties / action / enum
      Previous value: -[
-  "batch",
-  "chain",
-  "content",
-  "grep",
-  "query",
-  "select",
-  "subscribe",
-  "symbol",
-  "unsubscribe"
-]New value: +[
+  "batch",
+  "chain",
+  "query",
+  "select",
+  "semantic",
+  "subscribe",
+  "symbol",
+  "tql_execute",
+  "tql_schema",
+  "unsubscribe"
+]
    • 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. Changed1 schema field changedv1.25.0
    • addedInput schema / properties / kind
      Added value: +{
+  "description": "Symbol kind filter for action=symbol (default: any).",
+  "enum": [
+    "function",
+    "method",
+    "class",
+    "enum",
+    "variable",
+    "import",
+    "constant",
+    "any"
+  ],
+  "type": "string"
+}
  5. First observedv1.23.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is well covered. The description adds some interaction context, such as the help mechanism and the facade-style action routing, but it does not disclose additional behavioral traits like result shapes, subscription side effects, or permission requirements. No contradiction 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?

Two dense sentences. The first front-loads the tool's identity and available actions; the second gives the essential discovery path for exact action schemas. No filler, repetition beyond the action list, or unnecessary background is present.

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?

This is a high-complexity facade with 12 parameters, 11 actions, and no output schema. The description would normally be too thin, but the explicit instruction to call action=help with target_action for exact action schemas meaningfully compensates by giving the agent a reliable discovery path. Still, it does not summarize return values or per-action parameter requirements, so it is not fully complete.

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 input schema already explains all 12 parameters and their enums. The description adds one useful parameter-related instruction—combining action=help with target_action—but this is largely a restatement of the schema's target_action description. It does not meaningfully extend parameter understanding 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/codegraph-compatible search facade and lists the specific actions it supports. It is not a tautology and gives enough resource and operation context to distinguish it from navigation, edit, and project tools, though it does not explain what each action does.

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?

The description provides actionable discovery guidance: passing action=help with target_action returns the exact action schema. However, it does not state when to use this search facade versus sibling tools like nav, structure, viz, or edit, nor does it give exclusions or preference rules. Usage context is mostly implied through the action list.

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