Skip to main content
Glama

knowledge_reindex

Rebuild the document index to sync searchable Markdown notes with the shared SQLite store; set full=true to ignore cache and reread every file.

Instructions

Пересобрать индекс. full=true игнорирует кеш и перечитывает все файлы.

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": "knowledge_reindex"
  }
}

Input Schema

NameRequiredDescriptionDefault
fullNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior2/5

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

With no annotations, the description carries the full burden. It does disclose that full=true bypasses the cache and re-reads every file, which hints at runtime cost, but it says nothing about whether the index is unavailable during the rebuild, whether the operation is idempotent, what permissions are needed, or what gets returned.

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 short sentences, zero filler, with the operation stated first and the parameter behavior second. Every sentence earns its place.

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?

For a one-parameter, no-output-schema tool, the description covers purpose and the flag's effect, which is the minimum viable set. It falls short on safety/availability behavior and on routing guidance against seven sibling tools.

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?

Schema description coverage is 0%, so the description must explain the single parameter, and it does: full=true ignores the cache and re-reads all files, which is exactly the semantics the schema lacks. It does not state what full=false does explicitly (incremental/cached), which is the only small gap.

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?

"Пересобрать индекс" (rebuild the index) is a specific verb+resource pair, so the agent knows exactly what operation runs. However, nothing distinguishes it from siblings such as knowledge_commit or knowledge_append, which could plausibly also touch the index.

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 statement of when this tool should be invoked versus the other knowledge_* tools, no prerequisites, and no cost warning beyond the implicit hint in the full flag. The agent must infer that this is a maintenance/repair operation.

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