Skip to main content
Glama

Rebuild Vector Index

rebuild_vector_index

Rebuild the semantic search vector index from all existing journal entries to restore accurate search results when the index is missing, stale, or corrupted. Requires admin scope.

Instructions

[REQUIRES ADMIN SCOPE] Rebuild the semantic search vector index from all existing entries

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "rebuild_vector_index"
  }
}

Input Schema

NameRequiredDescriptionDefault
use_test_dbNo
project_numberNo

Output Schema

NameRequiredDescriptionDefault
codeNoError code (e.g. VALIDATION_ERROR, INTERNAL_ERROR)
errorNoHuman-readable error message
detailsNoAdditional error context
partialNo
successNo
categoryNoError category (validation, query, connection, internal)
suggestionNoSuggested fix for the error
recoverableNoWhether the error is recoverable
failedEntriesNo
entriesIndexedNo
aggregated_errorsNoDetails of individual errors in a multi-step operation

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv9.1.0
    • removedInput schema / properties / project_number / maximum
      Removed value: -9007199254740991
    • removedInput schema / properties / project_number / minimum
      Removed value: --9007199254740991
    • changedInput schema / properties / project_number / type
      Previous value: -"integer"New value: +[
      +  "number",
      +  "string"
      +]
  2. First observedv9.0.0

TDQS

B3/5.0
Behavior3/5

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

The '[REQUIRES ADMIN SCOPE]' prefix is genuine added value beyond the annotations, telling the agent an elevated permission is needed before calling. However, the description says nothing about what happens to the existing index (replaced, cleared first, or merged) and the annotations only mark it as non-read-only, non-idempotent, and non-destructive without clarifying the rebuild semantics.

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?

A single sentence with the permission requirement front-loaded before the action, which is the right order. It is not padded, though the brevity is partly the cause of the missing parameter and usage detail.

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?

An output schema exists, so return values need not be described, and the admin-scope note covers the biggest operational risk. Still, for a rebuild operation with two entirely undocumented parameters and no guidance on when to invoke it, the definition is thinner than the tool's complexity warrants.

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 description coverage is 0%, so neither of the two parameters is documented anywhere. The description does not explain 'use_test_db' or 'project_number', and 'use_test_db' is especially ambiguous — an agent cannot tell whether setting it targets a sandbox copy or changes the scope of the destructive rebuild.

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 a specific verb ('Rebuild') and a specific resource ('the semantic search vector index') plus its source ('from all existing entries'). This is enough to distinguish it from the incremental sibling add_to_vector_index, though it never names that sibling explicitly.

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

Usage Guidelines2/5

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

There is no stated condition for when to run a full rebuild versus an incremental add, no warning about how long it takes or whether search is degraded during the run. The agent must infer that 'rebuild' is the heavy-weight repair operation.

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