Skip to main content
Glama
Sign In
HomarUScc

HomarUScc

by kcdjmaxx
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

vault_reindex

Reindex your vault to keep it current. Incremental mode updates changed files; full mode rebuilds the entire index from scratch.

Instructions

Trigger a vault reindex. Default is incremental (only changed files). Use mode='full' to rebuild from scratch.

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

Input Schema

NameRequiredDescriptionDefault
modeNoReindex mode (default: incremental)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.0

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It goes beyond the bare minimum by explaining that default is incremental (only changed files) and full rebuilds from scratch, which gives useful insight into side effects. However, it does not mention potential performance impacts or whether the operation is reversible.

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?

The description is two sentences, front-loaded with the primary action, and every word earns its place. It is concise and well-structured without redundancy.

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

Completeness4/5

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

For a simple trigger tool with one parameter and no output schema, the description is largely complete. It explains the purpose, the default behavior, and the effect of the parameter. It could mention potential consequences or prerequisites, but given the low complexity, it is adequate.

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?

The schema already documents the 'mode' parameter with an enum and a brief description (100% coverage), so the baseline is 3. The tool description adds meaningful semantic detail by explaining what each mode does ('only changed files' vs 'rebuild from scratch'), adding value beyond the schema.

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 clearly states the verb 'Trigger' and resource 'vault reindex', making the action unambiguous. However, it does not explicitly distinguish this tool from siblings like vault_search or docs_compile, though the name itself is fairly distinct.

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?

The description implies usage when a reindex is needed and explains the two modes (incremental vs full), but it does not provide explicit when-to-use or when-not-to-use guidance, nor does it mention alternatives. The context is clear but not prescriptive.

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