Skip to main content
Glama
Sign In
omnara

omnara

Official
by omnara-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Go
Remote

List agents

agents_list
Read-onlyIdempotent

List a project's agents with current activity, newest first by default. Include archived agents or subagents only when requested.

Instructions

Lists the project's agents with their current activity, newest first by default. Archived agents and subagents are excluded unless requested.

Input Schema

NameRequiredDescriptionDefault
nameNoCase-insensitive glob over the list's logical name. `*` matches zero or more characters, `?` matches one character, and `\` escapes a wildcard.
sortNoSort order for named resources that expose created and modified timestamps.
limitNoMaximum number of items to return in one page.
orgIDYesOrganization ID (org_...).
cursorNoOpaque pagination cursor from a previous response's next_cursor. Omit for the first page.
projectIDYesProject ID (proj_...).
include_usageNoInclude each agent's `usage`, so a list can show costs without a request per agent.
parent_agent_idNoReturn only subagents spawned by this agent.
agent_profile_idNoReturn only agents launched from this agent profile.
include_archivedNoInclude archived agents. Defaults to false.
include_subagentsNoInclude subagents alongside top-level agents. Defaults to false, so only agents without a parent are returned unless parent_agent_id is set.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.1.1
    • addedInput schema / properties / orgID / description
      Added value: +"Organization ID (org_...)."
    • addedInput schema / properties / projectID / description
      Added value: +"Project ID (proj_...)."
  2. First observed

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, and non-destructive, covering the safety profile. The description adds useful default-exclusion behavior for archived agents and subagents, but doesn't mention pagination behavior or the inclusion of usage data despite that being a parameter.

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 sentences with zero waste, front-loading the primary action and default behavior. Every sentence earns its place.

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 list tool with rich schema coverage and read-only annotations, the description is nearly complete. It covers scope and defaults, but could mention that results are paginated with cursors, a key aspect for an agent consuming the output.

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%, so all parameters are already well-documented in the schema. The description adds only minor context about default sorting and exclusion, not enriching parameter meaning beyond what the schema provides.

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?

States a specific verb and resource ('Lists the project's agents') and adds scope detail about activity and ordering. It is clearly distinguishable from siblings like agents_get (single agent) and agents_archive (mutation).

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 description gives clear default behavior and a condition for expanding results (archived/subagents excluded unless requested), which implicitly guides filtering. However, it doesn't name alternatives like agents_get for fetching a single agent, so explicit routing to siblings is missing.

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

Deploy Server

Other Tools