Skip to main content
Glama

vexor_search

Describe the file or code you need in natural language. Get ranked results with paths, relevance scores, line ranges, and previews.

Instructions

Find files or code from a natural-language description. Returns ranked matches with paths, relevance scores, line ranges, and previews.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
topNoNumber of results to return.
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).
queryYesNatural-language description of the file or code you are looking for, e.g. 'where API retries are configured'.
no_cacheNoBuild a temporary in-memory index and disable all disk caches for this search. Slower and may regenerate embeddings.
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
pathYes
queryYes
staleYes
backendYes
resultsYes
rerankerYes
index_emptyYes
Behavior3/5

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

No annotations are provided, so the description must cover behavioral traits. It mentions 'ranked matches' indicating ranked results, but does not disclose performance, rate limits, or whether the tool is read-only. The non-destructive nature is implied but unstated.

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, front-loaded with the primary action and output details. Every word serves a purpose; no fluff.

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?

With an output schema (implied) and 10 parameters, the description is concise but covers the main functional purpose and return types. It could briefly mention the relationship with vexor_index (e.g., whether indexing is required) for fuller context.

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% and parameter descriptions are detailed (e.g., mode's enum values). The tool description adds minimal extra meaning beyond the schema; it reinforces the overall purpose but does not clarify specific parameters further.

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 clearly states the tool's purpose: 'Find files or code from a natural-language description' and lists the return values (ranked matches with paths, scores, line ranges, previews). It distinguishes from the sibling 'vexor_index' which likely manages indexes.

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 explains the tool is used for natural-language queries, but does not provide explicit when-to-use vs alternatives or when-not-to-use guidance. The sibling name offers a hint but is not discussed.

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