Skip to main content
Glama
Sign In
Stellaris MCP

Stellaris MCP

by GDM-Pixel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

reindex_file

Update the code index for a single modified or created file after editing, maintaining real-time index accuracy without a full reindex.

Instructions

Reindex a single file after it has been modified or created. Much faster than a full reindex — use this in hooks after Write/Edit tool calls to keep the index up-to-date in real time. Requires OPENAI_API_KEY.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "file": "<file>"
    },
    "name": "reindex_file"
  }
}

Input Schema

NameRequiredDescriptionDefault
fileYesAbsolute path to the modified file (e.g., "/home/user/project/src/foo.ts")

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv4.4.0

TDQS

A4.5/5.0
Behavior4/5

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

With no annotations provided, the description carries the full burden. It discloses that the operation is faster than a full reindex and requires an API key. It mentions keeping the index up-to-date, but does not detail side effects, idempotency, or error handling. Still, the behavioral context is fairly clear.

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?

The description is two sentences, front-loads the purpose, and contains no unnecessary words. Every sentence adds value.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's simplicity (one parameter, no output schema, no annotations), the description provides sufficient context: purpose, usage hooks, performance note, and a prerequisite. No gaps remain.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the schema already documents the single parameter 'file' with a clear description. The tool's description adds no additional parameter detail beyond what the schema provides, so a baseline of 3 is appropriate.

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 clearly states the tool's purpose (reindex a single file) and distinguishes it from a full reindex, which is a sibling tool. It specifies the context of use (after modification or creation).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

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

The description explicitly states when to use the tool ('after Write/Edit tool calls') and implies when not to (not for full reindex). It also notes a prerequisite: 'Requires OPENAI_API_KEY'.

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