jambavan

Overview Schema Source Related Servers Discussions Admin

jambavan_index

Builds or refreshes a code index via tree-sitter AST extraction and SQLite storage. Supports incremental file updates and returns indexing statistics.

Instructions

Build or refresh the Jambavan codebase index. Parses source files with a tree-sitter AST extractor and stores symbols in a local SQLite database. Run once per project, then incrementally on file changes. Returns indexing statistics (files processed, symbols extracted, duration).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "jambavan_index"
  }
}

Input Schema

Name	Required	Description	Default
`root`	No	Existing absolute directory inside the current fallback root. Re-points a previous tool-input root (needed by hosts that share one server across workspaces); cannot override an env, client-roots, or cwd-project binding.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv2.0.1Jul 30, 2026

changedInput schema / properties / root / description

Previous value: -"Existing absolute directory inside the current unresolved fallback root. Cannot override an already fixed env, client-roots, cwd-project, or tool-input binding."New value: +"Existing absolute directory inside the current fallback root. Re-points a previous tool-input root (needed by hosts that share one server across workspaces); cannot override an env, client-roots, or cwd-project binding."

Changed1 schema field changedv0.6.1Jul 13, 2026

addedInput schema / properties / root

Added value: +{
+  "description": "Existing absolute directory inside the current unresolved fallback root. Cannot override an already fixed env, client-roots, cwd-project, or tool-input binding.",
+  "type": "string"
+}

First observedv0.3.0Jul 4, 2026

TDQS

A4.2/5.0

Behavior4/5

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

No annotations provided, so description carries full burden. It discloses that the tool parses files, stores in SQLite, and returns statistics. It mentions incremental updates, which is good for an indexing tool. Lacks details on error handling or permissions, but acceptable.

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?

Three sentences, front-loaded with the primary action. Every sentence adds value: purpose, method, usage pattern, return value. No superfluous text.

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?

For an indexing tool with no output schema, the description adequately describes return values (statistics). It doesn't discuss resumption or cancellation, but the context is complete enough for an agent to use effectively.

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% with a single optional parameter 'root', which is already well-documented in the schema. The tool description adds no additional semantics beyond the schema, meriting the baseline score of 3.

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

Purpose5/5

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

The description explicitly states 'Build or refresh the Jambavan codebase index', using a specific verb+resource. It distinguishes from sibling tools like jambavan_awaken or jambavan_graph by focusing solely on indexing.

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?

Provides clear context: 'Run once per project, then incrementally on file changes.' This tells the agent when to invoke the tool. It does not explicitly list alternatives or exclusions, but the guidance is sufficient for typical use.

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