Skip to main content
Glama

zk_rebuild_index

Rebuild the database index by processing files in the Zettelkasten system, ensuring accurate note linking and efficient knowledge management.

Instructions

Rebuild the database index from files.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior2/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 states the action ('rebuild') but doesn't explain critical traits: whether this is a destructive operation (e.g., overwrites existing index), requires specific permissions, has performance impacts (e.g., time-consuming), or provides any output/confirmation. This leaves significant gaps for a tool that likely involves system-level changes.

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 a single, efficient sentence with zero wasted words. It's front-loaded with the core action and resource, making it easy to parse quickly, which is ideal for a tool with no parameters.

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

Completeness2/5

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

Given the complexity of a 'rebuild' operation (likely involving system changes), no annotations, and no output schema, the description is inadequate. It doesn't cover behavioral risks, expected outcomes, or error conditions, leaving the agent underinformed about how to use this tool safely and effectively.

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 tool has 0 parameters, and schema description coverage is 100%, so there's no need for parameter details in the description. The baseline for 0 parameters is 4, as the description appropriately doesn't waste space on nonexistent parameters, though it could theoretically mention why no inputs are needed (e.g., 'rebuilds using all available files').

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 action ('rebuild') and the target resource ('database index from files'), providing a specific verb+resource combination. However, it doesn't differentiate this tool from its siblings (like zk_find_orphaned_notes or zk_find_similar_notes that might involve index operations), which prevents a perfect score.

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?

The description provides no guidance on when to use this tool versus alternatives. There's no mention of prerequisites (e.g., when the index is corrupted), exclusions, or related tools (like zk_search_notes that might rely on the index), leaving the agent with no usage context.

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

Related 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/Liam-Deacon/zettelkasten-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server