Skip to main content
Glama
adepanges

TeamRetro MCP Server

list_teams

Retrieve and filter teams from TeamRetro using pagination. Specify team IDs or tags to narrow results and manage large datasets efficiently.

Instructions

List teams from TeamRetro with filtering and pagination

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNonumber
offsetNonumber
teamIdsNostring,string,...
teamTagsNostring,string,...

Implementation Reference

  • Core handler function `listTeams` in TeamsService that constructs query parameters from input and fetches the list of teams from the `/v1/teams` API endpoint.
    async listTeams(params?: {
      offset?: number;
      limit?: number;
      teamTags?: string;
      teamIds?: string;
    }): Promise<ListApiResponse<Team>> {
      const searchString = createSearchParams({
        offset: { value: params?.offset },
        limit: { value: params?.limit },
        teamTags: { value: params?.teamTags },
        teamIds: { value: params?.teamIds },
      });
    
      return this.get<ListApiResponse<Team>>(`/v1/teams?${searchString}`);
    }
  • Input schema for the `list_teams` tool, extending pagination schema with team-specific filters for tags and IDs.
    schema: paginationSchema.extend({
      teamTags: tagFilterSchema,
      teamIds: idFilterSchema,
    }),
  • Local registration of the `list_teams` tool within `teamTools`, including schema, description, and handler wrapper.
    list_teams: {
      schema: paginationSchema.extend({
        teamTags: tagFilterSchema,
        teamIds: idFilterSchema,
      }),
      description: "List teams from TeamRetro with filtering by tags and IDs, and pagination using offset and limit parameters",
      handler: async (args: {
        offset?: number;
        limit?: number;
        teamTags?: string;
        teamIds?: string;
      }) => createToolResponse(teamsService.listTeams(args)),
    },
  • src/tools.ts:13-22 (registration)
    Global tool registry that spreads `teamTools` (containing `list_teams`) into the main `tools` object for schema and handler export.
    const tools = {
      ...userTools,
      ...teamTools,
      ...teamMembersTools,
      ...actionTools,
      ...retrospectiveTools,
      ...agreementTools,
      ...healthModelTools,
      ...healthCheckTools,
    };
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It mentions 'filtering and pagination' which hints at capabilities, but fails to describe critical behaviors: whether this is a read-only operation, what authentication is required, rate limits, error conditions, or the structure of returned data. For a tool with 4 parameters and no output schema, this leaves significant gaps in understanding how the tool behaves.

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?

The description is a single, efficient sentence that front-loads the core purpose ('List teams from TeamRetro') followed by key capabilities ('with filtering and pagination'). Every word serves a purpose with zero redundancy or unnecessary elaboration, making it optimally concise for its informational content.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool has 4 parameters, no annotations, and no output schema, the description is insufficiently complete. While concise, it fails to address critical context: what authentication is needed, whether this is a safe read operation, what the return format looks like, or how filtering parameters interact. For a list tool with filtering capabilities, users need more guidance on expected behavior and results.

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 the schema already documents all parameters (limit, offset, teamIds, teamTags) with their types, constraints, and defaults. The description adds marginal value by mentioning 'filtering and pagination' which aligns with teamIds/teamTags and limit/offset parameters respectively, but provides no additional semantic context beyond what the schema already specifies.

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 clearly states the verb ('List') and resource ('teams from TeamRetro'), making the purpose immediately understandable. It distinguishes from siblings like 'detail_team' (which shows details of a specific team) and 'create_team' (which creates new teams). However, it doesn't explicitly differentiate from 'list_team_members' (which lists members within teams), leaving some ambiguity.

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?

The description implies usage context by mentioning 'filtering and pagination', suggesting this tool is for retrieving multiple teams with optional constraints. However, it provides no explicit guidance on when to use this versus alternatives like 'detail_team' for single teams or 'list_team_members' for team composition. The context is implied but not clearly articulated.

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

Install Server

Other Tools

Related Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/adepanges/teamretro-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server