Skip to main content
Glama

krusch_fs_sync

Idempotent

Indexes or refreshes workspace files into the structural page store so AI coding agents can retrieve current workspace documents and maintain grounded context.

Instructions

Index or refresh workspace files into the structural page store.

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

Input Schema

NameRequiredDescriptionDefault
pathsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.1

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds that files are written into a page store and that an existing index may be refreshed, but it does not say whether previously indexed pages absent from the new run are removed, how long indexing takes, or what the result reports.

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 front-loaded sentence with no filler, opening with the operative verb. Its brevity is appropriate for a one-parameter tool, though the jargon 'structural page store' does little work for an uninitiated agent.

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?

With annotations covering mutation safety and no output schema required, the definition is serviceable but leaves the key operational unknowns open: default scope when 'paths' is omitted and what happens to stale entries. For an indexing tool whose side effects persist, that is a meaningful gap.

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?

One optional parameter ('paths') with 0% schema description coverage, and the description says nothing about it. It omits whether omitting 'paths' indexes the entire workspace, whether entries are files, directories, or globs, and whether recursion applies, so the agent must guess at the default scope.

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?

States a concrete verb pair ('Index or refresh') and a concrete resource ('workspace files'), plus the destination ('structural page store'). This distinguishes it from read-only siblings such as krusch_fs_read_page and krusch_fs_search, though the description never names or contrasts those siblings 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?

No when-to-use guidance beyond the implied 'index files' intent. It does not say whether this must be run before krusch_fs_search or krusch_fs_locate can work, how often to refresh, or what to do instead if only a single page needs updating.

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