Skip to main content
Glama

Hail Communication for AI

List agents

list_agents
Read-onlyIdempotent

List the workspace's saved agents and their settings.

    Agent records contain IDs, names, instructions, greetings, disclosure settings,
    voice settings, enabled channels, status, duration limits and handover contacts.
    Returns ``items`` or an error.

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
llm_modelNoModel ID of the calling agent. Optional. Recorded for analytics only.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / llm_model
      Added value: +{
      +  "description": "Model ID of the calling agent. Optional. Recorded for analytics only.",
      +  "type": "string"
      +}
  2. First observed

TDQS

A3.7/5.0
Behavior4/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 covered. The description adds real value by enumerating what an agent record contains (IDs, names, instructions, greetings, disclosure/voice settings, channels, status, duration limits, handover contacts), which lets an agent decide whether one call suffices or whether a per-agent fetch is needed. The 'Returns items or an error' clause is largely redundant with the existing output schema.

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, front-loaded paragraphs: purpose first, record contents second. The closing 'Returns items or an error' sentence is filler given an output schema exists, but overall the text is tight with little wasted wording.

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?

The tool is simple: one optional analytics parameter, full annotations, and an output schema. The description covers scope, record payload, and error behavior, which is enough for correct invocation. It could be marginally stronger by explicitly pointing to get_agent for single-record lookups among the many siblings.

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?

There is a single optional parameter (llm_model) at 100% schema description coverage, and the schema already explains it is 'Recorded for analytics only'. The description adds nothing about this parameter, but with full schema coverage the baseline of 3 is appropriate.

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 the workspace's saved agents and their settings.' The plural 'list' plus 'saved agents and their settings' distinguishes it implicitly from get_agent (single record) and create_agent/delete_agent, though it never names the single-record alternative 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?

Usage is only implied by the verb choice — an agent can infer this is the bulk-retrieval call for agents. There is no explicit when-to-use versus when-not (e.g. 'use get_agent when you already have an ID'), so the agent must infer the routing from the verb alone.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources