Skip to main content
Glama
Sign In
folder-index

folder-index

by git-raka
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

index_status

Check indexed folders, file counts, last update time, and background re-indexing or OCR progress before running searches.

Instructions

Indexed folders, file counts, last update, and update/OCR progress.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.1

TDQS

C2.9/5.0
Behavior2/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 implies a read-only status query but never states that it is non-mutating, whether it requires the index to exist, whether calling it is expensive, or what happens while an update is in progress — the 'update/OCR progress' phrase hints at in-flight states without explaining them.

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 compact sentence with no filler and the key content front-loaded. It is slightly under-specified rather than verbose, so nothing needs trimming.

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?

An output schema exists, so the description does not need to explain return values — and indeed its field list largely duplicates that schema. What is missing is the operational framing: when to poll it, what 'progress' means, and its relationship to refresh_index. Adequate but with a clear gap for a zero-param monitoring tool.

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 takes zero parameters, so there is nothing for the description to disambiguate. The 4 baseline applies; the description's field list is arguably redundant with the output schema but harmless.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description enumerates what the tool surfaces ('Indexed folders, file counts, last update, and update/OCR progress'), so the subject matter is clear, but it is a bare noun phrase with no verb and never states plainly that this is a status/introspection read. It is distinguishable from siblings like refresh_index and search_files by content, though not by explicit contrast.

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 guidance on when to call this versus siblings such as refresh_index (which presumably triggers the update this tool reports on) or find_files. The agent must infer that this is a pre-check/monitoring call with no cost or prerequisite notes.

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