Skip to main content
Glama
Coval MCP Server

Coval MCP Server

Official
by coval-ai

Get agent

get_agent
Read-onlyIdempotent

Retrieve an agent's configuration by ID, including model type, voice phone number, endpoint status, and display name.

Instructions

Get agent config: model_type, phone_number (voice), whether a top-level endpoint is configured, and display_name.

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": {
      "agent_id": "<agent_id>"
    },
    "name": "get_agent"
  }
}

Input Schema

NameRequiredDescriptionDefault
agent_idYesThe unique ID of the agent to retrieve.

Schema Changelog

Changes observed during successful MCP inspections.

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

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 earns credit beyond that by naming the concrete fields returned — meaningful here because there is no output schema to convey the response shape. It stops short of covering not-found behavior or whether optional fields (phone_number) may be absent for non-voice agents.

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?

A single front-loaded sentence with the returned fields enumerated; no filler, no redundancy with the schema.

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?

With no output schema, listing the returned fields is exactly what the description needs to do, and it does so. Minor gaps remain around null/absent optional fields and error cases, but an agent has enough to call this correctly.

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?

Only one parameter and the schema documents it fully at 100% coverage, including pattern and length constraints. The description adds nothing about agent_id beyond what the schema states, so 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 (get agent config) and enumerates what the config contains: model_type, phone_number, endpoint-configured flag, display_name. It is clearly distinguishable from list_agents and update_agent, though it never names those siblings 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?

Retrieval by agent_id is implied by the required parameter and the 'Get' verb, but there is no explicit statement of when to call this versus list_agents or get_persona, and no preconditions or failure behavior are given.

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