Skip to main content
Glama
Coval MCP Server

Coval MCP Server

Official
by coval-ai

Get persona

get_persona
Read-onlyIdempotent

Retrieve persona details by ID—voice, language, background sound, behavior prompt, wait time, and conversation initiation—to configure agent conversations.

Instructions

Get persona details: voice_name, language_code (BCP-47), background_sound, persona_prompt (behavior), wait_seconds, conversation_initiation (speak_first/wait_for_user).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "persona_id": "<persona_id>"
    },
    "name": "get_persona"
  }
}

Input Schema

NameRequiredDescriptionDefault
persona_idYesThe unique ID of the persona to retrieve.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.4.1
    • changedInput schema / properties / persona_id / description
      Previous value: -"The unique ID of the persona to retrieve. Get this from list_personas."New value: +"The unique ID of the persona to retrieve."
    • addedInput schema / properties / persona_id / maxLength
      Added value: +128
    • addedInput schema / properties / persona_id / pattern
      Added value: +"^[A-Za-z0-9_-]+$"
  2. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive, and closed-world behavior. The description adds useful context by listing the persona fields returned, including behavior-related fields like persona_prompt and conversation_initiation, but it does not describe error behavior or not-found handling.

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 a single, front-loaded sentence that lists the relevant details without filler. Every phrase contributes to clarifying what the tool returns.

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 simple read-only tool with full annotation coverage and a complete input schema, the description is nearly complete because it lists the returned fields in the absence of an output schema. Minor gaps remain around error behavior and response shape, but the essential context is present.

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%, and the single parameter persona_id is fully documented in the schema. The description does not add any further meaning about persona_id, so it meets the baseline for full schema coverage.

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 uses a specific verb and resource ('Get persona details') and enumerates the details returned, making it clearly a single-persona retrieval tool. It is distinguishable from list_personas by the singular retrieval focus, even without naming the sibling explicitly.

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?

There is no guidance on when to use this tool versus alternatives such as list_personas, nor any prerequisites or exclusions. The retrieval use case is implied by the name and description but not explicitly stated.

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