Skip to main content
Glama
avarole-mcp
by Sbaig3229

avarole_list_agents

Read-only

Lists support agents with IDs, names, voices, and template status; search by name or ID and filter to ready-made templates for creating a new agent.

Instructions

List agents (assistants): id, name, voice, and whether it is a template. search matches the name or id. templates_only lists the ready-made templates a new agent can start from (see avarole_create_agent).

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": "avarole_list_agents"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
searchNo
templates_onlyNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds useful behavior (which fields come back, what search and templates_only do) but leaves match semantics ambiguous (substring vs. exact) and says nothing about ordering or pagination with `limit`.

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 resource and returned fields, then the two filter parameters. No filler or repetition of the tool name.

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 a valuable substitution and the annotations cover safety. The remaining gap is pagination/limit behavior for a list tool, which an agent may need in order to retrieve all agents.

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 0%, so the description must carry the load; it does explain `search` and `templates_only` meaningfully. However, `limit` is completely unaddressed — no indication of max page size, pagination, or what happens beyond the default 30.

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 (assistants)") and even enumerates the returned fields (id, name, voice, is-template), which lets an agent distinguish this from avarole_get_agent. It stops short of naming any sibling explicitly, so differentiation is implied rather than stated.

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

Usage Guidelines4/5

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

The definition explains the two filter modes and their purposes: `search` matches name or id, and `templates_only` surfaces ready-made templates for starting a new agent, cross-referencing avarole_create_agent. It gives clear usage context but no explicit when-not-to-use or alternative-routing guidance (e.g., use avarole_get_agent for a single agent's details).

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