Skip to main content
Glama

reindex

Rebuilds the wiki index after changes by re-embedding only modified notes, with an option to force full re-embedding.

Instructions

Wiki 변경 후 인덱스 재빌드 (변경된 노트만 re-embed).

Args: force: 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": "reindex"
  }
}

Input Schema

NameRequiredDescriptionDefault
forceNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full behavioral burden. It usefully discloses the default incremental behavior versus force-triggered full re-embedding, but it omits permissions, cost/duration, concurrency safety, idempotency, and side effects of rebuilding the index.

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?

The description is short, front-loaded with the purpose, and has no filler. The Args section is brief and useful, though it could be integrated more cleanly.

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 maintenance tool with an output schema, the description covers the core purpose and the force/default behavior. However, without annotations it still lacks operational context such as permissions, expected cost, and safety for repeated or concurrent calls.

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%, but the description explains force: true causes full forced re-embedding, while the default behavior re-embeds only changed notes. This adds meaningful semantics beyond the bare boolean schema, though it does not restate the default false value or optionality.

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 specifically states that it rebuilds the wiki index after changes and re-embeds changed notes, which clearly separates it from the CRUD, search, and link-management siblings. It is clear, though it does not explicitly contrast itself with an alternative maintenance tool.

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?

It gives a clear usage context: use after Wiki changes, with force for full re-embedding. It does not say when not to use it, whether changes should be batched, or what prerequisites or alternatives exist.

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