Skip to main content
Glama
importlens-mcp

importlens-mcp

by Matheos13

reindex

Rebuild the import graph index after files change on disk. Run it to keep symbol lookup results accurate when code has been added, moved, or edited.

Instructions

Rebuild the index. Call after you've changed files on disk.

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

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.2

TDQS

A3.9/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full disclosure burden. It usefully implies that the index can become stale and that this call is a state-mutating rebuild, but it says nothing about cost, duration, whether the operation blocks or locks concurrent readers, or whether it is incremental versus a full rebuild.

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?

Two short sentences, zero filler, with the action front-loaded and the trigger condition immediately following. Every sentence earns its place.

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

Completeness4/5

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

For a zero-parameter maintenance tool with an output schema already covering the return value, the description covers what it does and when to invoke it. The remaining gap is operational cost/blocking behavior, which matters for a rebuild but is not addressed.

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 and no risk of misleading argument hints. Baseline 4 applies for a parameterless tool.

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 and resource ('Rebuild the index'), so the agent knows exactly what operation occurs. It does not name any sibling or clarify which index/scope, but the sibling set (file_context, project_map, relevant_files) is unrelated enough that disambiguation is largely unnecessary.

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

Usage Guidelines4/5

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

'Call after you've changed files on disk' gives a concrete trigger condition, which is exactly the guidance an agent needs for a maintenance operation. There are no explicit exclusions (e.g., don't call repeatedly, don't call while reads are in flight), which keeps it from a 5.

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