Skip to main content
Glama

List AI agents

agent_list
Read-onlyIdempotent

Every AI agent configured for this organisation — what it is called, whether it is enabled, and whether it actually reached the voice runtime. An agent can exist here and answer no calls, so 'enabled' and 'reached_the_runtime' are different questions. Read only.

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

Input Schema

NameRequiredDescriptionDefault
include_archivedNoInclude archived agents. Omitted, only live ones are returned.

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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, idempotentHint and destructiveHint=false, so the safety profile is covered and the trailing 'Read only' is largely redundant. The description does add genuine domain context beyond annotations: that an agent can exist without answering calls, and that 'enabled' and 'reached_the_runtime' answer different questions — a real interpretive aid for the returned data.

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?

Three short sentences, front-loaded with the scope and the returned fields, with the enabled-vs-runtime distinction placed before the closing note. The final 'Read only' sentence duplicates the readOnlyHint annotation and could be dropped, but overall there is little waste.

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, the description usefully previews what each record contains and clarifies the meaning of two easily confused fields. For a single-optional-parameter read tool with full annotation coverage, nothing essential to correct invocation is missing.

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 include_archived is fully documented in the schema, including the default behaviour when omitted. The description adds nothing about the parameter, which is acceptable given the schema does the work, so the 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?

The description names the resource (AI agents configured for the organisation) and enumerates the fields returned (name, enabled, reached_the_runtime), so the agent knows this is a full listing rather than a single-record fetch. It does not explicitly name agent_detail as the alternative, so sibling differentiation is only implied by the word 'Every'.

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 implied by 'Every AI agent configured for this organisation', which suggests a broad enumeration, but there is no explicit statement of when to prefer this over agent_detail or agent_update. No exclusions or prerequisites are given.

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.