Skip to main content
Glama

groundcheck_get_report

Read-only

Retrieve a stored evaluation report using its ID. Choose between a concise summary or detailed results for each case.

Instructions

Fetch a previously persisted evaluation report by id.

Args:
    report_id: the id returned by groundcheck_run_suite.
    response_format: "concise" returns just the summary (scores,
        aggregates, worst cases). "detailed" returns every case's full
        faithfulness and retrieval results.

Raises an error listing available report ids if `report_id` is unknown.
No model calls -- reads from the local report store.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
report_idYes
response_formatNoconcise

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
casesYes
summaryYes
report_idNo
created_atNo
prompt_versionYes
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false. The description adds valuable context: it will raise an error listing available report IDs if an unknown ID is provided, and it clarifies that it reads from a local store without making API calls. This goes beyond the annotations.

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 composed of four concise sentences, front-loaded with the main purpose. Every sentence adds valuable information with no redundancy or fluff.

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 simplicity (fetching a report by ID), the description covers all necessary aspects: purpose, parameter usage, error behavior, and performance characteristics (no model calls). The presence of an output schema further complements the documentation.

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?

The description fully explains both parameters. For `report_id`, it specifies it is the id returned by `groundcheck_run_suite`. For `response_format`, it details the two enum values ('concise' for summary, 'detailed' for full results). Since the schema description coverage is 0%, the description carries the full burden and does so excellently.

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 explicitly states 'Fetch a previously persisted evaluation report by id.' It clearly identifies the verb (fetch) and the resource (evaluation report). The distinction from sibling tools like `groundcheck_run_suite` (which runs suites) and `groundcheck_evaluate_*` (which perform evaluations) is clear.

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 implies usage after running a suite by referencing `groundcheck_run_suite` for the report_id origin. It also mentions that no model calls are made, which suggests it is safe to use without cost. However, it does not explicitly state when to use this tool over alternatives or provide exclusion criteria.

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