Skip to main content
Glama

reindex

Refresh vector embeddings for knowledge base documents. Only re-embeds changed files by default; use full rebuild after changing the embedding model.

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
Behavior5/5

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

Discloses that it modifies vector index in place, does not modify source files, defaults to diff-aware re-embedding, and describes return values. Full burden carried since no annotations.

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?

Two paragraphs, front-loaded purpose, efficient sentences, no wasted words.

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 behavior, usage, parameters, and outputs sufficiently; no gaps given tool complexity and presence of output schema.

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

Parameters4/5

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

With 0% schema description coverage, the description adds crucial context for 'force' (when to use) and minimal but helpful context for 'project' (optional target name).

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?

Description clearly states 'Re-index the knowledge base docs into the vector store' and distinguishes from sibling tool git_pull_reindex by specifying when to use each.

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?

Provides explicit guidance: force=True is for changing embedding model, not routine; use git_pull_reindex() for git-pushed changes.

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