Skip to main content
Glama
LuisCarlosLopes

codesteer-atlas

atlas_search

Search code and documents using semantic hybrid search. Locate symbols or concepts by natural language or exact queries, returning metadata to identify exact lines before reading full content.

Instructions

Search code AND documents in the project's local index — your FIRST tool to find, explore or investigate anything here, before broad file reads or grep.

Runs a semantic hybrid search (vector + BM25, fused via RRF) over pre-indexed chunks of source code (classes/functions/methods) and documents (Markdown, text, JSON/YAML/ TOML). Pass natural language or exact symbols. For a structural overview instead, use atlas_map.

Token-efficient two-pass pattern: by default this returns metadata only (file_path, lines, symbol, type, score). Locate first, then read the exact lines with Read, or re-call with include_content=true for the few results whose content you actually need.

Call directly — do NOT call atlas_status first "just to check". If the index does not exist yet, this raises an actionable error explaining how to build it (see atlas_index).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
repoNoOptional repository name filter.
limitNoAlias for 'top_k'; overrides it when provided.
queryYesNatural language description or exact symbols to find.
top_kNoMax results, 1-50. Defaults to 5.
languageNoOptional language filter (e.g. 'python', 'javascript', 'go').
path_prefixNoOptional path prefix filter (e.g. 'src/controllers').
include_contentNoWhen true, includes each result's 'content'. Defaults to false (metadata/location only) to save tokens.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

No annotations provided, but description fully discloses the search algorithm, default metadata-only return, optional content inclusion, and error handling when index is missing.

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?

Well-structured with clear front-loading of purpose. Every sentence adds value; no redundancy.

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 complexity, full schema coverage, and output schema existence, the description is complete. It covers algorithm, usage pattern, error handling, and sibling relationships.

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?

Schema coverage is 100%, but description adds value by explaining the two-pass pattern, token-saving via include_content, alias for limit, and query flexibility (natural language or symbols).

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?

Clearly states it searches code and documents using semantic hybrid search. Distinguishes from sibling tools atlas_map and atlas_index.

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?

Explicitly recommends this as the first tool to use before broad file reads or grep, advises against calling atlas_status first, and provides a two-pass pattern for token efficiency.

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