Skip to main content
Glama
Coval MCP Server

Coval MCP Server

Official
by coval-ai

List personas

list_personas
Read-onlyIdempotent

List simulated personas with voice, language, background sound, and behavior prompt details so you can select or review test users for evaluation runs.

Instructions

List personas (simulated users). Each has voice_name, language_code, background_sound, and a behavior prompt.

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

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 simulated personas"
    • 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

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds what a persona is made of (voice_name, language_code, background_sound, behavior prompt), which is useful context but not operational behavior such as pagination or result limits.

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?

Two short sentences, front-loaded with the purpose before the field list. There is no filler, though the brevity leaves obvious seams the description could have filled.

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 read-only list tool with full schema coverage and annotations covering safety, the definition is largely sufficient. With no output schema, naming the returned persona fields is a genuine contribution; only pagination behavior is left unstated.

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 filter, order_by, page_size, and page_token are fully documented in the schema (including syntax examples and bounds). The description adds no parameter meaning of its own, so the baseline of 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 personas') and glosses the concept as 'simulated users', which an agent can distinguish from get_persona without opening either schema. No explicit sibling differentiation beyond the list/get naming convention.

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 by the verb 'List' – there is no statement of when to call this versus get_persona, nor any exclusions or prerequisites. An agent can infer it enumerates the collection, but nothing routes it explicitly.

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