Skip to main content
Glama
LuisCarlosLopes

codesteer-atlas

atlas_search

Find relevant code snippets using hybrid search that combines vector similarity and keyword matching to locate specific implementations or concepts in indexed codebases.

Instructions

Perform a semantic hybrid search on the indexed source code.

This tool combines vector similarity (cosine) and full-text keyword search (BM25) to find the most relevant code snippets (chunks) based on the user's query intent. Use this tool when looking for specific implementations, where functions or features are defined, or to locate code matching a certain concept or task.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYesThe natural language search term or description of the code to find.
top_kNoMaximum number of results to return (integer between 1 and 50). Defaults to 5.
repoNoOptional repository name to filter results.
languageNoOptional programming language to filter results (e.g., 'python', 'javascript', 'go').
path_prefixNoOptional file path prefix to restrict the search to a specific directory (e.g., 'src/controllers').
include_contentNoWhen false, omits the 'content' field from results to save tokens, returning only metadata and location (file_path, lines, symbol, type, language, score). Defaults to true.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

No annotations provided, but description discloses search algorithm (cosine + BM25), token optimization with include_content, and that it returns code snippets. Lacks details on prerequisites (indexed data) or rate limits.

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 front-loaded sentences covering functionality, algorithm, and usage context. No redundant or filler content.

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?

Given the presence of an output schema, the description sufficiently covers purpose and usage. Could optionally mention need for prior indexing, but overall adequate.

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 description coverage is 100%, so baseline is 3. Description does not add extra parameter details beyond the schema's own descriptions, which are already clear.

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 it performs a semantic hybrid search on indexed source code, combining vector and keyword search. This distinguishes it from sibling tools like indexing or status checks.

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?

Explicitly states when to use (searching for implementations, functions, concepts). Does not mention alternatives or when not to use, but context from siblings is inferable.

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