Skip to main content
Glama
LuisCarlosLopes

codesteer-atlas

by LuisCarlosLopes
OverviewSchemaRelated ServersScoreDiscussions
Python
Local

atlas_index

Index source code into a local search index for semantic code search. Supports incremental updates and optional full re-indexing.

Instructions

Index (or re-index) source code into the local search index.

IMPORTANT: unless the user already specified what to index, call with dry_run=true first, show the candidate folders to the user and ASK whether to index everything or specific folders. Only then call again with the chosen 'paths' (or none for the full workspace).

Indexing is incremental by default: unchanged files are skipped on subsequent calls, making re-runs fast. Use full=true to force a complete rebuild ignoring cached file hashes.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
workspaceNoAbsolute path to the root directory to index. Defaults to the parent directory of the resolved index, or the current working directory if no index has been resolved yet. Must exist and be a directory.
pathsNoOptional list of subfolder paths, relative to 'workspace', to index (e.g. ["src", "docs"]). When omitted, the entire workspace is indexed. Each path must resolve to a location inside 'workspace' (no path traversal).
fullNoWhen true, forces a full re-index ignoring cached file hashes. Defaults to false (incremental).
dry_runNoWhen true, does NOT index anything. Instead, returns the top-level candidate folders under 'workspace' with a count of eligible files in each, so the agent can present them to the user before deciding what to index. Defaults to false.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Tool Definition Quality

A4.9/5.0
Behavior5/5

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

With no annotations provided, the description fully covers behavioral traits: incremental indexing by default, full rebuild with full=true, dry_run returns candidates, and path constraints. It discloses the incremental optimization and the workflow expectations transparently.

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 well-structured with a bolded warning, clear sections, and no unnecessary sentences. It front-loads the main purpose and important workflow note, making it easy to parse quickly.

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 4 optional parameters, no required params, and an output schema (not shown but present), the description covers all needed context: purpose, workflow, parameter semantics, incremental vs full. Nothing critical is omitted.

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 describes each parameter (100% coverage), so the description adds value by explaining the dry_run workflow and how paths relate to user decision-making. This elevates it above the baseline 3.

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 'Index (or re-index) source code into the local search index' with specific verb and resource. It distinguishes indexing from sibling tools like atlas_search and atlas_map by focusing on the indexing action and incremental behavior.

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 provides explicit workflow guidance: use dry_run=true first to show candidate folders, ask the user, then call with chosen paths or none for full workspace. This is exceptional usage advice that goes beyond typical tool descriptions.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/LuisCarlosLopes/codesteer-atlas'

If you have feedback or need assistance with the MCP directory API, please join our Discord server