Skip to main content
Glama

list_sub_agents

Read-onlyIdempotent

Lists sub-agents registered under a parent agent—direct children by default, or the full descendant subtree with recursive=true.

Instructions

List the sub-agents registered under an agent (see register_sub_agent): direct children only, or the whole subtree with recursive=true. get_team_directory lists every member of the workspace instead.

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_sub_agents"
  }
}

Input Schema

NameRequiredDescriptionDefault
agent_idNoUUID of the parent agent whose sub-agents to list. Omit for the calling agent; get_team_directory gives other agents' ids.
recursiveNoReturn all descendants (up to 10 levels deep) instead of direct children only. Default false.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.1.6
    • changedInput schema / properties / agent_id / description
      Previous value: -"Parent agent ID. Defaults to the calling agent."New value: +"UUID of the parent agent whose sub-agents to list. Omit for the calling agent; get_team_directory gives other agents' ids."
    • changedInput schema / properties / recursive / description
      Previous value: -"Return all descendants (up to 10 levels deep)."New value: +"Return all descendants (up to 10 levels deep) instead of direct children only. Default false."
  2. First observedv0.1.1

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and non-destructive, so safety is covered; the description adds genuine scope behavior beyond that (children only vs. full subtree, plus the parent-agent default when agent_id is omitted). It stops short of describing result shape or any depth-limit behavior in the description itself, so it is not exhaustive.

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 dense sentences, zero filler, with the core behavior and both sibling disambiguations front-loaded before any edge case.

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 no-output-schema list tool with zero required parameters, the definition covers purpose, scope, recursion behavior and alternatives. The only mild gap is that it does not hint at what a returned entry contains (id, name, status), which would help an agent decide whether to recurse.

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 coverage is 100%, so both parameters are already fully documented, including the 10-level depth cap and the 'omit for calling agent' default. The description reinforces the direct-children vs. recursive distinction but adds no syntax or format detail the schema does not already carry, so the baseline 3 applies.

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 (list sub-agents registered under an agent) and immediately disambiguates from two siblings by name: register_sub_agent for creation and get_team_directory for workspace-wide membership. An agent can distinguish all three without opening a schema.

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

Usage Guidelines5/5

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

Explicit routing: use this for direct children by default, set recursive=true for the whole subtree, and use get_team_directory instead when you want every member of the workspace. Both the when-to-use and the when-to-use-something-else conditions are stated.

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