Skip to main content
Glama

groundcheck_run_suite

Read-only

Run faithfulness and retrieval quality evaluation over a batch of RAG pipeline cases, producing a summary report with mean metrics and worst-performing cases.

Instructions

Run faithfulness (+ retrieval, where gold labels exist) over a batch of cases.

Use this to evaluate a whole RAG pipeline run rather than one answer at a
time. Supply exactly one of `cases` or `dataset_path`.

Args:
    cases: inline list of {id, query, answer, sources, relevant_ids?}.
    dataset_path: path to a JSONL file of the same case objects, one per
        line. Must resolve inside the allowlisted data directory (env
        GROUNDCHECK_DATA_DIR, default cwd) -- paths outside it are rejected.
    k_values: retrieval cutoffs (default [3, 5, 10]).

Persists a full report and returns a summary (mean faithfulness, mean
NDCG, worst 5 cases, report_id). Fetch the full report with
groundcheck_get_report(report_id). Cost scales with case count: ~2 model
calls per case via your client's sampling.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
casesNo
k_valuesNo
dataset_pathNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
mean_ndcgNo
report_idYes
case_countYes
worst_casesYesIds of the 5 lowest-faithfulness cases.
mean_faithfulnessYes
Behavior4/5

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

Annotations already mark as readOnly. Description adds cost info ('~2 model calls per case'), report persistence path, and how to retrieve the full report. No contradictions.

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 first sentence stating purpose, then usage note, then parameter descriptions. Slightly verbose with the Args block but overall efficient.

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 purpose, parameters, behavior, cost, and return structure. References related tool for full report. Lacks detail on output schema but given it's provided separately, it's sufficient.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, but description fully explains each parameter: cases as inline list format, dataset_path with directory restriction, k_values with defaults. Adds critical meaning beyond the schema.

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 tool runs faithfulness (+ retrieval) over a batch of cases, distinguishing it from siblings like groundcheck_evaluate_faithfulness which likely handles single cases. Explicitly says 'evaluate a whole RAG pipeline run rather than one answer at a time.'

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 this to evaluate a whole RAG pipeline run' and 'Supply exactly one of cases or dataset_path.' Doesn't explicitly mention when not to use or alternatives, but the context is clear enough.

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/offquestxo/groundcheck'

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