Skip to main content
Glama

list_standups

Retrieve and display all standup configurations including name, channel, questions, participants, and schedule. Understand team structures and progress tracking processes.

Instructions

Retrieves and displays all Geekbot standups a user has access to, including their complete configuration details such as name, channel, questions, participants, and schedule information. Use this tool to understand the structure of the team and the processes they use track progress and sync.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function 'handle_list_standups' that executes the tool logic: calls gb.get_standups(), filters out paused/draft standups, parses them via standup_from_json_response, and returns a JSON text response with count and standup details.
    async def handle_list_standups(gb: GeekbotClient) -> list[types.TextContent]:
        """List all standups of a Geekbot user
    
        Returns:
            str: Properly formatted JSON string of standups list
        """
        standups = await gb.get_standups()
        parsed_standups = [
            standup_from_json_response(s).model_dump()
            for s in standups
            if not s["paused"] and not s["draft"]
        ]
        return [
            types.TextContent(
                type="text",
                text=json.dumps(
                    {
                        "number_of_standups": len(parsed_standups),
                        "standups": parsed_standups,
                    }
                ),
            )
        ]
  • The Tool definition (types.Tool) for 'list_standups', including name, description, and inputSchema (empty object, no required params).
    list_standups = types.Tool(
        name="list_standups",
        description="Retrieves and displays all Geekbot standups a user has access to, including their complete configuration details such as name, channel, questions, participants, and schedule information. Use this tool to understand the structure of the team and the processes they use track progress and sync.",
        inputSchema={"type": "object", "properties": {}, "required": []},
    )
  • Registration: list_standups is included in the list_tools() function that returns all available tools.
    def list_tools() -> list[types.Tool]:
        return [
            list_members,
            list_standups,
            fetch_reports,
            post_report,
            list_polls,
            fetch_poll_results,
        ]
  • Registration: The run_tool() function handles 'list_standups' by dispatching to handle_list_standups.
    case "list_standups":
        return await handle_list_standups(gb_client)
  • Helper function standup_from_json_response that parses a raw dict response into a Standup model.
    def standup_from_json_response(s_res: dict) -> Standup:
        channel = s_res["channel"]
        if not channel:
            channel = "confidential standup - dm with user"
    
        return Standup(
            id=s_res["id"],
            name=s_res["name"],
            channel=channel,
            time=s_res["time"],
            timezone=s_res["timezone"],
            questions=[question_from_json_response(q) for q in s_res["questions"]],
            participants=[user_from_json_response(p) for p in s_res["users"]],
            owner_id=s_res["master"],
            confidential=s_res["confidential"],
            anonymous=s_res["anonymous"],
        )
Behavior3/5

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

No annotations are provided, so the description must disclose behaviors. It mentions returning configuration details but lacks details on pagination, performance, or limitations. Adequate but not thorough.

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 sentences: first states action and scope, second gives usage guidance. No wasted words.

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?

Given no output schema and no annotations, the description is mostly complete for a zero-param retrieval tool. It could mention pagination or return structure limitations.

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?

Input schema has no parameters, so the description need not add param info. Baseline 4 is appropriate.

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 that it retrieves all Geekbot standups with configuration details, using a specific verb+resource. It distinguishes from siblings like list_members and list_polls.

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 provides a usage context ('understand structure of the team and processes') but does not explicitly compare to alternatives or give when-not-to-use guidance.

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