Skip to main content
Glama
Coval MCP Server

Coval MCP Server

Official
by coval-ai

List metrics

list_metrics
Read-onlyIdempotent

Retrieve available evaluation metrics that define how agent performance is measured, with optional built-in metrics and filtering or sorting.

Instructions

List available evaluation metrics. Metrics define how agent performance is measured. Set include_builtin=true to see built-in metrics.

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_metrics"
  }
}

Input Schema

NameRequiredDescriptionDefault
filterNoFilter expression (e.g., status="COMPLETED")
order_byNoSort order (e.g., "-create_time" for newest first)
page_sizeNoNumber of results per page (1-100, default 50)
page_tokenNoToken for retrieving the next page of results
include_builtinNoInclude built-in metrics in results (default false)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.5.0
    • removedInput schema / additionalProperties
      Removed value: -false
  2. Changed4 schema fields changedv0.4.1
    • addedInput schema / description
      Added value: +"Input for listing available metrics"
    • addedInput schema / properties / filter / maxLength
      Added value: +1000
    • addedInput schema / properties / order_by / maxLength
      Added value: +200
    • addedInput schema / properties / page_token / maxLength
      Added value: +2048
  3. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, so the safety profile is covered. The description adds that built-in metrics are excluded by default, which is useful behavioral context, but says nothing about result volumes, ordering defaults, or pagination behavior beyond what the schema documents.

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?

Three short sentences, front-loaded with the action and free of filler. The middle sentence on metric definition is marginally expendable but adds conceptual orientation for an unfamiliar resource.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a zero-required-parameter read tool with a fully documented schema, the essentials are present. However, with no output schema, the description does not indicate what a returned metric object looks like or whether results are paginated, leaving the agent to infer the response shape.

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 all five parameters are already self-documenting with examples. The description only restates include_builtin, which is fully documented in the schema, and says nothing about filter, order_by, or page_size semantics.

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?

The description gives a specific verb+resource ('List available evaluation metrics') and adds a definitional sentence about what metrics are. It does not explicitly distinguish itself from sibling get_metric or the python_metric_draft tools, but the 'list' vs 'get' split is inferable.

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 only implied: 'Set include_builtin=true to see built-in metrics' tells the agent how to widen the query, but there is no statement of when to use this versus get_metric or the metric-draft tools.

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