Skip to main content
Glama
CronusL-1141

AI Team OS

by CronusL-1141
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

team_list

Retrieve and filter teams—active by default—newest first, with pagination and compact rows to navigate long team lists. Switch to full details when needed.

Instructions

List teams — active ones by default, newest first.

Default response is a COMPACT projection (view="compact" + hint - trimmed, NOT missing fields): each row keeps id / name / status / kind / project_id / created_at. Teams accumulate one row per Workflow run and per CC session, so the list is long: filter by status and page with limit / offset.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMax teams to return (default 50, capped at 200)
fieldsNo"compact" (default, trimmed rows) / "all" (full team rows)compact
offsetNoPagination offset (default 0)
statusNoFilter by lifecycle status - "active" (default) / "completed" / "archived" / "" for every teamactive

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv1.11.2
    • addedInput schema / properties / fields
      Added value: +{
+  "default": "compact",
+  "description": "\"compact\" (default, trimmed rows) / \"all\" (full team rows)",
+  "type": "string"
+}
    • addedInput schema / properties / limit
      Added value: +{
+  "default": 50,
+  "description": "Max teams to return (default 50, capped at 200)",
+  "type": "integer"
+}
    • addedInput schema / properties / offset
      Added value: +{
+  "default": 0,
+  "description": "Pagination offset (default 0)",
+  "type": "integer"
+}
    • addedInput schema / properties / status
      Added value: +{
+  "default": "active",
+  "description": "Filter by lifecycle status - \"active\" (default) / \"completed\"\n/ \"archived\" / \"\" for every team",
+  "type": "string"
+}
  2. First observedv1.9.0

TDQS

A4/5.0
Behavior4/5

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

With no annotations, the description carries the full behavioral burden and does meaningful work: it explains that teams accumulate one row per Workflow run and per CC session, so the list is long and paging is expected, and it clarifies that compact output is trimmed rather than lossy. It never states read-only safety or auth requirements, but 'List' plus the paging guidance covers the important non-obvious traits.

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?

Front-loads the purpose and default, then explains the projection and the paging need in three tight sentences. Every sentence earns its place, though the parenthetical 'view="compact" + hint - trimmed' is slightly clunky phrasing.

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?

An output schema exists, so return values need not be described, and the description still covers defaults, filtering, and pagination behavior adequately. The only material gap is the absence of any statement about read-only safety or permissions, which matters since there are no annotations.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, and the description adds real meaning beyond the schema by justifying the default compact projection ('trimmed, NOT missing fields') and enumerating the retained columns, which clarifies what the fields parameter actually buys. It does not add format details for status values or the limit cap beyond what the schema already says.

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 teams') plus scope and ordering ('active ones by default, newest first'). It does not name any sibling such as team_status or agent_list, so an agent gets a clear purpose but no explicit differentiation from the other list/status tools in the family.

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?

Gives clear context for use: the default active filter, and the advice to 'filter by status and page with limit / offset' because the list grows long. It stops short of saying when to prefer team_status or another sibling, so there are no explicit exclusions or alternatives.

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