Skip to main content
Glama
Coval MCP Server

Coval MCP Server

Official
by coval-ai

List reports

list_reports
Read-onlyIdempotent

Retrieve saved evaluation reports for the authorized organization, returning paginated report summaries and a continuation token for accessing additional results.

Instructions

List saved evaluation reports in the authorized organization. Returns a bounded page of report summaries and a continuation token when more are available.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_reports"
  }
}

Input Schema

NameRequiredDescriptionDefault
page_sizeNoNumber of reports to return (1-100, default 50).
page_tokenNoToken for retrieving the next page of reports.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.5.0
    • removedInput schema / additionalProperties
      Removed value: -false
  2. Addedv0.4.1

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds real value beyond that: it discloses the authorization scoping and the pagination contract (bounded page of summaries plus a continuation token when more exist), which annotations cannot express.

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?

Two sentences, zero waste. Scope is front-loaded and the return contract follows immediately, so an agent can read the whole thing in one pass.

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?

For a two-parameter read tool with no output schema, the description covers what an agent needs: scope, page bounds, and the continuation token for further pages. It stops short of characterizing what fields a "report summary" contains, a minor gap given no output schema exists.

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 coverage is 100%, with page_size bounds/default and page_token format fully documented in the schema, so the baseline is 3. The description reinforces the continuation-token concept but adds no parameter syntax or defaults beyond what the schema already says.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ("List saved evaluation reports") plus a scope constraint ("in the authorized organization"). The list/get distinction from get_report and create_report is clear from the verb, though no sibling is named explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied rather than stated: an agent infers this is the enumeration entry point for reports. There is no explicit when-to-use guidance, no mention of when to prefer get_report, and no preconditions (e.g. whether reports must exist).

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.