Skip to main content
Glama
CronusL-1141

AI Team OS

by CronusL-1141
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

team_status

Retrieve a team's status summary with member and active task details, using a compact default view and options to include offline members and adjust limits.

Instructions

Get a team's status summary — team info + members + active tasks.

Default response is a COMPACT projection (view="compact" + hint - trimmed, NOT missing fields): member and task rows are projected, offline members fold into a count plus digest, and at most 30 active tasks are listed (the remainder is reported in active_tasks_omitted; task_list_project with team_id lists them all).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMax member rows to return after the offline split (default 30, capped at 200)
fieldsNo"compact" (default, trimmed rows) / "all" (full member and task rows)compact
team_idYesTeam ID or team name
include_offlineNoInclude offline members as rows instead of a count plus digest (default False)
offline_previewNoHow many most-recent offline members to show in the digest (default 5; ignored when include_offline is True)

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 member and task rows)",
+  "type": "string"
+}
    • addedInput schema / properties / include_offline
      Added value: +{
+  "default": false,
+  "description": "Include offline members as rows instead of a count\nplus digest (default False)",
+  "type": "boolean"
+}
    • addedInput schema / properties / limit
      Added value: +{
+  "default": 30,
+  "description": "Max member rows to return after the offline split (default 30,\ncapped at 200)",
+  "type": "integer"
+}
    • addedInput schema / properties / offline_preview
      Added value: +{
+  "default": 5,
+  "description": "How many most-recent offline members to show in the\ndigest (default 5; ignored when include_offline is True)",
+  "type": "integer"
+}
  2. First observedv1.9.0

TDQS

A4.1/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 burden and does disclose response-shaping behavior: offline members fold into a count plus digest, at most 30 active tasks are returned with the remainder surfaced in active_tasks_omitted. It does not touch permissions or read-only status, though "Get" implies a read.

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?

The purpose is front-loaded in one clear sentence, followed by a dense but information-rich paragraph on the default projection. It is generally efficient, though the parenthetical jargon ("view='compact' + hint - trimmed, NOT missing fields") costs some readability.

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 and coverage is high, so return values need not be explained, and the description still clarifies the projection and omission behavior. For a read-only summary tool it is nearly complete, missing only explicit read-only/auth context.

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 the schema already documents every parameter (limit, fields, team_id, include_offline, offline_preview), giving a baseline of 3. The description adds the projection/cap context but also introduces a terminology mismatch by referencing view="compact" when the actual parameter is fields="compact".

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+resource ("Get a team's status summary") and enumerates the payload contents (team info + members + active tasks), which cleanly separates it from team_list and task_list_project. An agent can distinguish it from siblings without reading the schema.

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 routes the agent to task_list_project when the full task list is wanted, and clarifies that the default is a trimmed projection essentially indicating when the compact view suffices. It does not explicitly contrast against team_list, so it falls short of a fully explicit when-to-use/when-not statement.

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