Skip to main content
Glama

Rebuild Index

rebuild_index

Rebuilds the full index of the official skills directory to refresh searchable catalog entries. Use it when skills are added or changed and AI clients must find current content by relevance.

Instructions

Força a reindexação completa do diretório oficial de skills.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose that this is a forced full rebuild rather than an incremental one. It says nothing about whether existing index data is destroyed during the rebuild, expected duration, whether reads are blocked while it runs, or what permissions are needed. That is a real gap for a likely expensive mutation, though the 'complete' framing gives some useful signal.

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?

A single sentence with no filler, and the key qualifier ('completa') is placed where it reads first. Nothing is redundant or buried. The only minor note is that the description is in Portuguese while the surrounding tooling is English.

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?

The tool is simple (no parameters) and has an output schema, so return values need no explanation. However, for a forced rebuild of a shared directory, an agent still needs to know cost, side effects on concurrent readers, and whether it is safe to call repeatedly. Those are absent.

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 no parameter meaning to convey and the baseline of 4 applies. The schema trivially matches the description's parameterless nature.

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 names a specific verb and resource: forcing a complete reindex of the official skills directory. The scope word 'completa' distinguishes it from an incremental refresh. It does not explicitly contrast itself with siblings like search_installed_skills or promote_draft, 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 Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no statement of when to invoke this versus the other skill-registry tools, nor any precondition such as 'use after installing or editing a skill'. The verb 'Força' hints at an exceptional, deliberate action, but the agent must infer that entirely.

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