Skip to main content
Glama

list_agent_teams

Read-only

List AI Agent Studio teams with their member agents, memory scope, and run frequency for read-only auditing and team oversight.

Instructions

AI Agent Studio teams (sn_aia_team) with their member agents and memory scope (sn_aia_team_member), and how often each team ran (sn_aia_execution_plan). 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": "list_agent_teams"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoTeam name contains
limitNoMax teams (default 25)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv5.1.0

TDQS

A3.5/5.0
Behavior3/5

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

The 'Read-only' sentence merely restates readOnlyHint=true and earns no credit. The description does add one genuine behavioral fact beyond annotations: results aggregate three tables, joining teams with their members and execution-plan run counts, so the caller knows it is a cross-table read rather than a flat listing. Volume, ordering, and truncation behavior are unaddressed.

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?

A single dense sentence with the resource stated first and the payload detail following; no filler and nothing redundant. The inline table identifiers add precision rather than noise, though they could be less prominent.

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 two-optional-parameter read-only list tool with no output schema, the description covers the return content (members, memory scope, run counts) and the safety profile is carried by annotations. Only the shape of nested member data and result ordering remain unspecified, which is a minor gap.

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 both parameters (name, limit) are already documented in the schema, including the default of 25. The description contributes no additional meaning such as whether 'name' is case-sensitive or how limit interacts with the joined member rows. 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 a specific verb and resource ('AI Agent Studio teams') and enumerates exactly what each entry carries: member agents, memory scope, and execution frequency. The parenthetical table names (sn_aia_team, sn_aia_team_member, sn_aia_execution_plan) pin down the underlying objects. It does not explicitly contrast itself with siblings such as list_ai_agents or list_agent_memory, which keeps it below 5.

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?

No explicit when-to-use or when-not-to-use statement, and no named alternatives among the many list_agent_* siblings. Usage is only implied by the described payload: reach for this when you need team composition plus run frequency. An agent can infer the scenario but gets no routing guidance.

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