Skip to main content
Glama

reindex

Update the vector index for knowledge base documents. Re-embeds only changed files by default, or rebuild all embeddings from scratch when forcing a full reindex.

Instructions

Re-index the knowledge base docs into the vector store.

    Modifies the vector index in place. Does not modify source .md files.
    By default only re-embeds changed files (fast, diff-aware). Set
    force=True to rebuild all embeddings from scratch — use this after
    changing the embedding model, not for routine updates.

    Use git_pull_reindex() instead when the docs changes came from a
    git push to the knowledge repo.

    Args:
        force: Rebuild all embeddings from scratch, not just changed files
               (default: False — use only when changing embedding model)
        project: Target project name (optional)

    Returns:
        Files indexed, changed, skipped; chunks upserted; stale chunks removed.
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
forceNo
projectNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

Describes in-place modification, no source file changes, diff-aware default, and force rebuild behavior. Mentions stale chunk removal but lacks potential side effects or auth details. With no annotations, description carries full burden and does well.

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?

Well-structured with intro, bullet points, and returns section. Not overly verbose, but could be slightly more compact.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Covers purpose, behavior, parameters, and return values. Output schema exists but description's Returns section is sufficient. No missing information for a reindex tool.

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

Parameters5/5

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

Schema coverage is 0%, so description compensates fully. Explains force parameter (purpose and when to use) and project parameter (target project). Adds meaning beyond schema defaults and types.

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 'Re-index the knowledge base docs into the vector store' with specific verb and resource. It distinguishes from sibling tool git_pull_reindex by noting its better fit for git-push changes.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly advises when to use force=True (after changing embedding model) and when to prefer git_pull_reindex (for git-sourced changes). Provides clear default behavior (diff-aware).

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/dl4rce/flaiwheel'

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