Skip to main content
Glama
Sign In
turbocontext

turbocontext

by e-x-h-i-b-i-t
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

index_workspace

Index code files recursively in a directory using Tree-sitter AST chunking and vector storage, skipping unchanged files unless force is enabled.

Instructions

Recursively finds code files in directory_path and indexes them using Tree-sitter AST chunking,
FastEmbed vector generation, and Turbovec storage. Skips unchanged files automatically unless force=True.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "workspace_id": "<workspace_id>",
      "directory_path": "<directory_path>"
    },
    "name": "index_workspace"
  }
}

Input Schema

NameRequiredDescriptionDefault
forceNo
workspace_idYes
directory_pathYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

No annotations provided, so description carries burden. Discloses recursive file discovery, specific indexing pipeline (Tree-sitter, FastEmbed, Turbovec), and auto-skip behavior. Missing side-effect or permission info.

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 sentences are efficient and focused, no filler. Information is front-loaded.

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?

Has output schema, so return values not needed. However, no error cases, prerequisites, or success conditions described. Adequate but not thorough for 3-param tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, so description should compensate. It mentions force=True meaning and implies directory_path is a folder path, but workspace_id is unexplained beyond name. Minimal parameter guidance.

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?

Description clearly states the tool indexes code files in a directory using specified technologies. It distinguishes from siblings like search_code by being the indexing step, but does not explicitly differentiate.

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?

Provides guidance on skipping unchanged files and force parameter, but lacks explicit when-to-use vs alternatives like search_code or prerequisites.

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