Skip to main content
Glama

search

Read-onlyIdempotent

Search indexed code and documentation using natural-language queries. Returns ranked results with file signatures for quick triage, or full code bodies for immediate use.

Instructions

Semantic + lexical (hybrid) search over an indexed source. This is your PRIMARY search tool — use it FIRST for any question about the indexed code or docs. Omit source to search ALL sources at once (rankings fused via RRF, each hit tagged with its source); pass source to target one. Configured sources: . Best practices: use natural-language descriptions of what the code does, not exact identifiers (use grep for those). Good: 'method that handles player damage calculation'. Bad: 'CalculateDamage'. Args: query (natural language); source (optional name); top_k (default from config); file_glob, extensions, path_contains (optional filters). For broad/exploratory queries, or a large top_k, set outline=true to get signatures-only results (much cheaper to read): scan them, then pull just the one body you need with find_definition or its file:line. Use the default (full bodies) when you'll work with the code right away.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYesNatural-language description of the behavior to find (e.g. 'method that handles player damage calculation'), NOT an identifier — use grep for exact names.
top_kNoMaximum number of results to return. Defaults to the server's configured value.
sourceNoSource name from `list_sources`. Omit to use the default: all sources for `search`/`deep_search` (RRF-fused), or the single applicable source for the others.
outlineNoIf true, return each hit's signature + first doc line instead of its full body — cheap triage for broad queries or a large top_k. Scan the signatures, then read the one body you need (find_definition, or its file:line). Default false = full bodies, for when you'll use the code right away.
file_globNofnmatch glob to restrict results by path/filename, e.g. `*.cs` or `**/Editor/*`.
extensionsNoRestrict results to these file extensions, e.g. `['.cs', '.shader']`.
path_containsNoKeep only results whose file path contains this substring.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive. Description adds behavioral details: RRF fusion when searching all sources, per-hit source tagging, outline mode for cheaper triage. No contradictions. Adds context beyond annotations.

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?

Well-structured with clear sections: function, usage hierarchy, best practices, parameter summary, advanced outline usage. Every sentence serves a purpose, though slightly verbose. Efficient for the amount of information conveyed.

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?

Covers main search behavior, source handling, filters, and alternative return format (outline). Doesn't detail errors or output structure, but output schema likely covers that. Given the tool's complexity and features, it is fairly complete.

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%, baseline 3. Description adds value by clarifying the intent of each parameter (e.g., query should be natural language, source omission implies all sources RRF-fused, outline use cases). These nuances go beyond schema descriptions.

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 semantic + lexical hybrid search over an indexed source. It positions itself as the PRIMARY search tool, distinguishing from siblings like deep_search and grep for exact identifiers. The scope (all sources vs. single source) and best practices are explicit.

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?

Provides explicit guidance: 'use it FIRST for any question', recommends natural language over identifiers, advises when to use outline mode vs full bodies. Does not directly contrast with deep_search beyond implying it is secondary, but still strong guidance.

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/lorenzo-cambiaghi/LynxMCP'

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