Skip to main content
Glama
phillipkaraya

rageval-mcp

retrieve

Read-onlyIdempotent

Retrieve top-k passages from a sample RAG corpus using various retrieval methods to see what context a RAG system would surface for a query.

Instructions

Retrieve the top-k passages for a query from the bundled sample corpus.

Use this to see *what context a RAG system would surface* for a question, and how that
changes with the retrieval method. The corpus is a fictional B2B SaaS knowledge base that
ships with the server, so no setup or data is required.

Args:
    query: The natural-language question or search string.
    k: How many passages to return (1 to 20).
    method: One of 'bm25', 'tfidf', 'dense', or 'hybrid' (default 'hybrid').

Returns:
    RetrieveResult with fields:
        - query (str), method (str), k (int), count (int)
        - passages: list of {rank, doc_id, chunk_id, score, text}, best first.

Raises:
    A tool error if method='dense' but the optional 'sentence-transformers' extra is not
    installed; the message explains how to enable it.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYesNatural-language query to search the corpus.
kNoNumber of passages to return.
methodNoRetrieval strategy: 'bm25' (lexical), 'tfidf' (lexical, idf-weighted), 'dense' (sentence-embedding similarity, needs the optional dense extra), or 'hybrid' (reciprocal-rank fusion of the available retrievers).hybrid

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYes
methodYes
kYes
countYes
passagesYes
Behavior4/5

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

Annotations declare readOnlyHint=true, destructiveHint=false, idempotentHint=true. The description adds beyond annotations by explaining the bundled corpus (no setup) and error behavior for missing dense extra. This provides useful behavioral context not available from annotations alone.

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?

The description is concise with clear sections (overview, Args, Returns, Raises). Every sentence adds value; no fluff. It is well-structured and front-loaded with the core purpose.

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 tool's complexity (3 parameters, output schema implied by Returns section), the description is complete. It covers return fields, error cases, and usage context. Annotations are rich, and the description provides adequate supplementary information.

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. The description's 'Args' section restates schema info concisely but adds no new meaning beyond what the schema already provides. The error message hint is helpful but not parameter-specific.

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 the action ('Retrieve the top-k passages for a query') and the resource ('bundled sample corpus'). It distinguishes from sibling tools (compare_methods, evaluate_retrieval) by specifying that it is for simple retrieval to see context surfaced by a RAG system.

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?

The description explicitly says 'Use this to see what context a RAG system would surface' and notes that no setup is required. It implies when to use but does not explicitly state alternatives or when not to use. The context signal includes sibling tools, but no direct comparison is provided.

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/phillipkaraya/rageval-mcp'

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