Skip to main content
Glama

index_update

Re-index a repository after file edits or for a never-scanned folder to scan changed files and refresh stale claims.

Instructions

Re-index after editing files (a never-scanned folder: the first scan); claims on changed files become stale.

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_update"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare non-read-only, non-idempotent and non-destructive, so the safety bar is lower. The description adds real value by disclosing a side effect beyond the annotations: existing claims on changed files become stale. It doesn't say whether the call blocks, how expensive it is, or what is returned.

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 the trigger and the consequence, no filler. The parenthetical could be rephrased more plainly, but nothing is wasted.

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 no parameters, no output schema and annotations covering the safety profile, the definition is close to complete. It still leaves the meaning of 'claims' and the consequences of non-idempotency unexplained, which matters for a mutating indexing operation.

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 schema to describe and no parameter semantics to compensate for. Baseline 4 applies.

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 specific verb+resource ('Re-index') and the trigger ('after editing files'), plus the edge case of a never-scanned folder. It does not differentiate from siblings like analyze or code_check, so it stops short of a 5.

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?

Two usage conditions are implied: after file edits, and first scan on an unscanned folder. However, no alternatives are named (e.g., when to use analyze or code_check instead) and the parenthetical is telegraphic enough to be ambiguous about which condition applies.

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