Skip to main content
Glama

coolify_teams

Manage Coolify teams by listing teams, viewing current team details, retrieving specific team information, and listing team members through structured actions.

Instructions

Complete team management - list teams, get current team, get team details, and list team members

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
actionYesAction to perform: list (list all teams), current (get current team), get (get specific team), members (list team members)
team_idNoTeam ID (required for get and members actions, optional for others)

Implementation Reference

  • The core handler function implementing 'coolify_teams' tool logic. Handles actions: list (GET /teams), current (GET /teams/current), get (GET /teams/{teamId}), members (GET /teams/{teamId}/members or current). Returns JSON-formatted API responses.
    async teams(action: string, teamId?: string) {
      switch (action) {
        case 'list':
          const response = await this.apiClient.get('/teams');
          return { content: [{ type: 'text', text: JSON.stringify(response.data, null, 2) }] };
        case 'current':
          const currentResponse = await this.apiClient.get('/teams/current');
          return { content: [{ type: 'text', text: JSON.stringify(currentResponse.data, null, 2) }] };
        case 'get':
          if (!teamId) throw new Error('Team ID is required for get action');
          const getResponse = await this.apiClient.get(`/teams/${teamId}`);
          return { content: [{ type: 'text', text: JSON.stringify(getResponse.data, null, 2) }] };
        case 'members':
          const endpoint = teamId ? `/teams/${teamId}/members` : '/teams/current/members';
          const membersResponse = await this.apiClient.get(endpoint);
          return { content: [{ type: 'text', text: JSON.stringify(membersResponse.data, null, 2) }] };
        default:
          throw new Error(`Unknown teams action: ${action}`);
      }
    }
  • Tool definition including name, description, and input schema for validating parameters (action enum and optional team_id).
      name: 'coolify_teams',
      description: 'Complete team management - list teams, get current team, get team details, and list team members',
      inputSchema: {
        type: 'object',
        properties: {
          action: { 
            type: 'string', 
            enum: ['list', 'current', 'get', 'members'],
            description: 'Action to perform: list (list all teams), current (get current team), get (get specific team), members (list team members)'
          },
          team_id: { 
            type: 'string', 
            description: 'Team ID (required for get and members actions, optional for others)' 
          },
        },
        required: ['action'],
      },
    },
  • src/index.ts:92-93 (registration)
    Tool call dispatcher in handleToolCall switch statement that routes 'coolify_teams' invocations to the teams handler.
    case 'coolify_teams':
      return await this.handlers.teams(args.action, args.team_id);
  • src/index.ts:60-64 (registration)
    Registers all tools (including coolify_teams) for listTools request by returning getTools() array.
    this.server.setRequestHandler(ListToolsRequestSchema, async () => {
      return {
        tools: getTools(),
      };
    });
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions actions but doesn't describe behavioral traits such as required permissions, rate limits, response formats, or whether operations are read-only or mutative. For a tool with multiple actions, this is a significant gap in transparency.

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 description is a single, efficient sentence that lists all key actions without unnecessary words. It's front-loaded with the main purpose ('Complete team management') and structured clearly. However, it could be slightly more polished by using bullet points or clearer formatting for the actions.

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's complexity (multiple actions), lack of annotations, and no output schema, the description is incomplete. It doesn't address behavioral aspects, usage context, or return values, leaving gaps that could hinder an AI agent's ability to use the tool effectively in a broader 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?

The schema description coverage is 100%, with clear descriptions for both parameters (action and team_id). The description doesn't add any additional semantic context beyond what's in the schema, such as examples or edge cases. Since the schema does the heavy lifting, the baseline score of 3 is appropriate.

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 tool's purpose as 'Complete team management' and enumerates four specific actions (list teams, get current team, get team details, list team members), providing a comprehensive overview. However, it doesn't explicitly differentiate this team management tool from sibling tools like coolify_projects or coolify_servers, which prevents a perfect score.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives. It lists actions but doesn't specify prerequisites, contexts, or comparisons to sibling tools (e.g., when to use coolify_teams vs. coolify_projects for related data). This lack of usage context limits its effectiveness for an AI agent.

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

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/HowieDuhzit/CoolifyMCP'

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