Skip to main content
Glama
Coval MCP Server

Coval MCP Server

Official
by coval-ai

List agents

list_agents
Read-onlyIdempotent

Retrieve configured AI agents for evaluation, optionally filtered and sorted by status or creation time. Supports pagination to browse voice, SMS, WebSocket, and chat agents.

Instructions

List agents (AI systems to evaluate). Model types: VOICE, OUTBOUND_VOICE, SMS, WEBSOCKET, and CHAT.

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

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

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 configured agents"
    • 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.3/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, and openWorldHint=false, so the safety profile is fully covered by structured data. The description adds domain context (what an agent is, which model types exist) but says nothing about result volume, pagination behavior, or ordering defaults. That is a modest addition over annotations, not a rich one.

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 short sentences, front-loaded with the core verb+resource, zero filler. Nothing is repeated from the title beyond the necessary verb.

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?

With four fully-documented optional parameters and complete annotations, an agent can call this correctly. However, with no output schema, the description should say something about what a result looks like (fields, default ordering, page_size default behavior) and it does not. Adequate but with a real gap for a list tool.

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 four parameters (filter, order_by, page_size, page_token) are already documented with examples in the schema. The description's model-type list is a mildly useful hint about filterable values, but it never names the field to filter on, so it doesn't meaningfully extend parameter semantics. Baseline 3 applies.

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 agents") and clarifies the domain object as "AI systems to evaluate", which an agent could not infer from the name alone. It also enumerates the model types (VOICE, OUTBOUND_VOICE, SMS, WEBSOCKET, CHAT), further pinning down the resource. It does not explicitly contrast with the sibling get_agent, but the list/get distinction is self-evident.

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

Usage Guidelines2/5

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

The description gives no guidance on when to use this versus get_agent, list_runs, or the other list_* siblings, and no note about pagination strategy or typical filtering workflow. Usage is only implied by the verb "List".

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