Skip to main content
Glama
Sign In
CodeGuard

CodeGuard

by Skhaaall
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

reindex

Rebuild the project index for CodeGuard analysis. Use incremental mode to re-parse only changed files, reducing re-indexing time.

Instructions

Re-indexe le projet. Par defaut complet, avec incremental=true ne re-parse que les fichiers modifies.

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

Input Schema

NameRequiredDescriptionDefault
incrementalNoSi true, ne re-parse que les fichiers modifies depuis le dernier indexage (plus rapide)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.2

TDQS

A3.5/5.0
Behavior2/5

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

No annotations exist, so the description must carry full behavioral disclosure. It does explain the full vs incremental re-indexing behavior, but omits side effects on the existing index, potential cost or duration, and whether reindexing is destructive or safe.

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, compact sentence front-loads the core action and clearly communicates both the default mode and the parameter option. No unnecessary words or repetition.

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?

For a simple one-optional-parameter tool, the description covers the core operation and the parameter's effect, and no output schema is present to require return-value details. However, with no annotations and no guidance on when to invoke it, the contextual picture is only minimally complete.

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 input schema already documents the incremental parameter with 100% coverage, but the description adds the crucial default behavior ('Par defaut complet') that the schema does not state. This clarifies what happens when the parameter is omitted.

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

Purpose5/5

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

The description states a specific action and resource: 'Re-indexe le projet'. It also distinguishes behavior by default vs incremental, making the tool's role clear even among many siblings.

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 guidance is provided on when to use reindex versus alternatives like status, check, guard, or impact. The description explains the incremental option but not the context or prerequisites that should trigger this tool.

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