Skip to main content
Glama

list_members

Lists all team members participating in standups and polls, enabling users to identify their colleagues.

Instructions

Lists all team members participating in the standups and polls of the user. Use this tool to get information about the colleagues of the user

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function `handle_list_members` that executes the tool logic: fetches standups, extracts unique participants, and returns JSON with member count and details.
    async def handle_list_members(gb: GeekbotClient) -> list[types.TextContent]:
        """List all members of participants in the standups and pollsof the user
    
        Returns:
            str: Properly formatted JSON string of members list
        """
        standups = await gb.get_standups()
        participants = []
        for s in standups:
            standup_obj = standup_from_json_response(s)
            participants.extend(standup_obj.participants)
    
        unique_participants = list(set(participants))
        unique_participants_json = [p.model_dump() for p in unique_participants]
        return [
            types.TextContent(
                type="text",
                text=json.dumps(
                    {
                        "number_of_members": len(unique_participants),
                        "members": unique_participants_json,
                    }
                ),
            )
        ]
  • The tool definition (types.Tool) with name='list_members', description, and inputSchema (empty object, no required params).
    list_members = types.Tool(
        name="list_members",
        description="Lists all team members participating in the standups and polls of the user. Use this tool to get information about the colleagues of the user",
        inputSchema={"type": "object", "properties": {}, "required": []},
    )
  • Tool is listed in `list_tools()` function which returns all available tools including list_members.
    def list_tools() -> list[types.Tool]:
        return [
            list_members,
  • Tool dispatch in `run_tool()`: case 'list_members' calls handle_list_members(gb_client).
    match name:
        case "list_members":
            return await handle_list_members(gb_client)
  • Server-level registration via @server.call_tool() which delegates to run_tool().
    @server.call_tool()
    async def handle_call_tool(
        name: str, arguments: dict | None
    ) -> list[types.TextContent | types.ImageContent | types.EmbeddedResource]:
        return await run_tool(gb_client, name, arguments)
Behavior2/5

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

No annotations are provided, and the description only implies read-only behavior. It does not disclose permissions, limits, or any side effects, failing to compensate for missing annotations.

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?

Two brief sentences convey the purpose and usage without any unnecessary words. Every sentence adds value.

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?

For a simple list tool with no parameters, the description adequately covers what it returns and its context. Lack of output schema is acceptable for such a straightforward function.

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?

With 0 parameters, the baseline is 4. The description adds no further parameter information, but none is needed.

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?

The description clearly states the verb ('Lists') and the resource ('team members participating in standups and polls'). It distinguishes from siblings like list_polls and list_standups by focusing on members.

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?

Provides guidance to 'get information about colleagues' but lacks explicit when-not-to-use or alternatives. The sibling tools are different enough that confusion is unlikely.

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/geekbot-com/geekbot-mcp'

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