Skip to main content
Glama

atlas_search

Read-onlyIdempotent

Search indexed documentation sections with BM25 full-text ranking to locate broad or multi-section topics, returning ranked anchor-linked snippets for follow-up reads.

Instructions

Run a BM25 full-text search across documentation sections and return ranked snippets with anchors.

Use this tool for broad or multi-section topics ('where all is armor mentioned?') or when
`atlas_where` returns no single match. Pass a returned `anchor` to `atlas_read` to inspect the full section.

Behavior & Output:
- Read-only lexical search via SQLite FTS5 (no embeddings; project synonyms come from `.atlas/aliases.yml`).
- Returns a JSON string `{query, count, hits: [{anchor, title, path, line, snippet, score}]}`.
  Returns `count: 0` and an empty `hits` list if nothing matches.

Input Schema

NameRequiredDescriptionDefault
kNoMaximum number of ranked section hits to return (1-50, default 5).
docNoOptional document ID (e.g. 'combat' or '02-combat') to restrict the search to a single document. Omit or pass null to search all documents.
queryYesKeywords or phrase to search across all indexed documentation sections (e.g. 'cover reduction', 'turn order'). Uses lexical FTS5 matching with umlaut folding ('Hoehe' matches 'Höhe') and German compound splitting.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changedv0.1.1
    • addedInput schema / properties / doc / description
      Added value: +"Optional document ID (e.g. 'combat' or '02-combat') to restrict the search to a single document. Omit or pass null to search all documents."
    • addedInput schema / properties / k / description
      Added value: +"Maximum number of ranked section hits to return (1-50, default 5)."
    • addedInput schema / properties / k / maximum
      Added value: +50
    • addedInput schema / properties / k / minimum
      Added value: +1
    • addedInput schema / properties / query / description
      Added value: +"Keywords or phrase to search across all indexed documentation sections (e.g. 'cover reduction', 'turn order'). Uses lexical FTS5 matching with umlaut folding ('Hoehe' matches 'Höhe') and German compound splitting."
    • addedInput schema / properties / query / minLength
      Added value: +1
  2. First observedv0.1.0

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), and the description adds real substance beyond them: the search is lexical FTS5 with no embeddings, synonyms come from `.atlas/aliases.yml`, and the zero-result case returns `count: 0` with an empty hits list. That tells an agent both the retrieval model and how to interpret an empty response.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the action, then usage, then a labeled 'Behavior & Output' block — easy to scan with no filler. The output-shape sentence is somewhat redundant given an output schema exists, which keeps it from a perfect score.

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?

Covers mechanism, selection criteria, sibling routing, alias configuration, and empty-result semantics for a three-parameter read tool. Nothing an agent needs before calling it or after receiving hits is missing.

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 `k`, `doc`, and `query` are already fully documented including ranges, defaults, and the umlaut-folding/compound-splitting note. The description adds no parameter-level meaning beyond the schema, so the baseline 3 applies.

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?

States a specific mechanism and resource: a BM25 full-text search across documentation sections returning ranked snippets with anchors. The example query and the boundary against `atlas_where` make it instantly distinguishable from siblings.

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?

Explicit when-to-use ('broad or multi-section topics'), an explicit fallback condition ('when `atlas_where` returns no single match'), and an explicit next step ('pass a returned anchor to `atlas_read`'). The routing to two sibling tools is fully specified.

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