Skip to main content
Glama
andyliszewski

grounding-ai

search_corpus

Find relevant information from your knowledge base using semantic search, retrieving document chunks that match your query for accurate answers.

Instructions

Search the agent's corpus for relevant documents using semantic similarity. Returns chunks from ingested PDFs, EPUBs, and documents that match the query. Use this to find information in your knowledge base before answering questions.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYesNatural language search query
agentYesAgent name (e.g., 'scientist', 'ceo'). Determines which filtered corpus to search.
top_kNoNumber of results to return (default: 5, max: 20)
rerank_enabledNoWhether to apply cross-encoder reranking after FAISS. When true, FAISS fetches a candidate pool (rerank_pool_size) and a cross-encoder produces the final top-k ordering. Off by default; see CLAUDE.md for the latency/quality trade-off.
rerank_pool_sizeNoFAISS candidate count fed to the reranker; higher pool = better quality, slower. Default 50. Ignored unless rerank_enabled is true.
rerank_modelNoOverride the default reranker model name (default: 'BAAI/bge-reranker-base'). Ignored unless rerank_enabled is true.BAAI/bge-reranker-base
hybrid_enabledNoWhether to fuse FAISS + BM25 via RRF before (optional) rerank. Off by default. See CLAUDE.md 'Hybrid Retrieval' for when to enable and the latency/quality trade-off.
hybrid_pool_sizeNoCandidates fetched from each channel (FAISS and BM25) before fusion; higher = better recall, slightly slower. Default 50. Ignored unless hybrid_enabled is true.
hybrid_k_rrfNoRRF damping constant (default 60; literature standard). Raising it flattens rank contributions. Ignored unless hybrid_enabled is true.
Behavior3/5

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

No annotations, so description carries full burden. It explains search returns chunks, but does not disclose read-only nature, rate limits, or authentication. Schema details conditional parameters, but description lacks behavioral context beyond results.

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?

Three concise sentences: purpose, result type, usage context. No fluff, front-loaded with core action. Every sentence adds value.

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 9 parameters with conditional logic and no output schema, description is reasonably complete. Covers what the tool does and types of documents. References external docs for trade-offs, but lacks brief guidance on choosing hybrid vs rerank.

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 3. Description adds minimal meaning beyond schema, only rephrasing 'semantic similarity' and document types. Does not clarify parameter relationships or trade-offs.

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?

Description clearly states verb 'Search', resource 'the agent's corpus', and method 'semantic similarity', with specific document types (PDFs, EPUBs). Distinguishes from sibling tool 'list_corpus_agents' which lists agents, not search.

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 advises use for 'find information in your knowledge base before answering questions.' Does not specify when not to use or mention sibling as alternative, but context implies distinct purposes.

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/andyliszewski/grounding-ai'

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