Skip to main content
Glama

vexor_index

Build or refresh a semantic index for a directory, enabling semantic search across files with configurable granularity modes.

Instructions

Build or refresh the semantic index for a directory. Use it to warm the cache or when auto_index is disabled.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
modeNoIndex granularity: auto routes per file type; name embeds filenames only; head/full/brief cover content depth; code chunks by AST; outline chunks Markdown by headings.auto
pathNoDirectory to operate on. Absolute, or relative to the server's default path (/app).
localNoCreate <path>/.vexor and store this project's index there
recursiveNoRecurse into subdirectories (default). Set false to scan only the top level of the directory.
extensionsNoOnly include these file extensions, e.g. ['.py', '.md'].
include_hiddenNoInclude dot-prefixed files and directories such as .github or .env (excluded by default).
exclude_patternsNoGitignore-style patterns to exclude.
respect_gitignoreNoHonor .gitignore rules (default). Set false to also scan ignored files such as build output.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
modeYes
pathYes
statusYes
files_indexedYes
Behavior2/5

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

No annotations are provided, so the description must fully disclose behavioral traits. It only says 'Build or refresh,' lacking details on destructiveness (e.g., whether refresh overwrites), auth requirements, rate limits, or side effects. This leaves significant gaps for an AI agent.

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?

The description is two sentences, very concise, and front-loaded with the core purpose. Every word earns its place with no fluff.

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?

The description is short but covers the basic purpose. With 8 parameters and an output schema, it could mention how the output is structured or reference the sibling tool for fuller context. It is adequate but not thorough.

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 already documents all parameters. The tool description adds no additional parameter information beyond what is in the schema, meeting the baseline but not exceeding it.

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 states 'Build or refresh the semantic index for a directory,' which is a specific verb+resource. It adds context with 'warm the cache or when auto_index is disabled,' but does not explicitly distinguish from its sibling tool 'vexor_search,' though the purpose seems distinct enough.

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?

The description provides clear usage scenarios (warm cache, auto_index disabled), giving context for when to use the tool. However, it does not mention when not to use it or alternatives like the sibling tool, which keeps it from a 5.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/scarletkc/vexor'

If you have feedback or need assistance with the MCP directory API, please join our Discord server