Skip to main content
Glama
sakce

Monday.com MCP Server

by sakce

monday-get-board-groups

Retrieve groups from a specific Monday.com board using the board ID. This tool enables efficient management and organization of board data within the Monday.com MCP Server.

Instructions

Get the Groups of a Monday.com Board.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
boardIdYesMonday.com Board ID that the Item or Sub-item is on.

Implementation Reference

  • The handler function that fetches and returns the groups for a given Monday.com board ID using the Monday SDK.
    async def handle_monday_get_board_groups(
        boardId: str, monday_client: MondayClient
    ) -> list[types.TextContent]:
        """Get the Groups of a Monday.com Board."""
        response = monday_client.groups.get_groups_by_board(board_ids=boardId)
        return [
            types.TextContent(
                type="text",
                text=f"Got the groups of a Monday.com board. {json.dumps(response['data'])}",
            )
        ]
  • Registers the MCP tool 'monday_get_board_groups' with @mcp.tool(), handling input validation via type hints and delegating to the core handler.
    @mcp.tool()
    async def monday_get_board_groups(boardId: str) -> str:
        """Get the Groups of a Monday.com Board.
    
        Args:
            boardId: Monday.com Board ID that the Item or Sub-item is on.
        """
        try:
            client = get_monday_client()
            result = await handle_monday_get_board_groups(boardId, client)
            return result[0].text
        except Exception as e:
            return f"Error getting board groups: {e}"
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 states it's a 'Get' operation, implying read-only behavior, but doesn't specify if it requires authentication, returns paginated results, or handles errors. This is inadequate for a tool with no annotation coverage.

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 directly states the tool's purpose without unnecessary words. It's appropriately sized and front-loaded, making it easy to parse quickly.

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

Completeness3/5

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

Given the tool's low complexity (1 parameter, no output schema, no annotations), the description is minimally adequate but lacks depth. It doesn't explain what 'Groups' are in Monday.com context or what the return format might be, which could hinder an agent's ability to use it effectively without trial and error.

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 the 'boardId' parameter fully. The description doesn't add any extra meaning beyond what's in the schema, such as example usage or constraints, but the baseline is 3 when schema coverage is high.

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 action ('Get') and resource ('Groups of a Monday.com Board'), making the purpose understandable. However, it doesn't differentiate from sibling tools like 'monday-list-items-in-groups' or 'monday-get-board-columns', which also retrieve board-related data but focus on different resources.

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?

No guidance is provided on when to use this tool versus alternatives. For example, it doesn't mention if this should be used before creating items in groups or as a precursor to 'monday-move-item-to-group', leaving the agent to infer usage from the tool name alone.

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/sakce/mcp-server-monday'

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