Skip to main content
Glama

fetch_reports

Retrieve standup reports to analyze team updates, track progress, or compile summaries. Filter by standup ID, user, or date range.

Instructions

Retrieves Geekbot standup reports. Use this tool to analyze team updates or updates from specific colleagues, track progress, or compile summaries of standup activities. This tool is usually used after the list_standups tool.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
standup_idNoID of the specific standup to fetch reports for. If not provided, reports for all standups will be fetched.
user_idNoID of the specific user to fetch reports for. If not provided, reports for all members will be fetched.
afterNoFetch reports after this date (format: YYYY-MM-DD)
beforeNoFetch reports before this date (format: YYYY-MM-DD)

Implementation Reference

  • The handler function that executes the fetch_reports tool logic: calls the Geekbot API to get reports, parses them, and returns JSON with report count, reports data, and unique reporter count.
    async def handle_fetch_reports(
        gb_client: GeekbotClient,
        standup_id: int | None = None,
        user_id: int | None = None,
        after: str | None = None,
        before: str | None = None,
    ) -> list[types.TextContent]:
        """Fetch reports list from Geekbot
    
        Args:
            standup_id: int, optional, default is None and means for all standups. The standup id to fetch reports for
            user_id: int, optional, default is None and means for all members. The user id to fetch reports for
            after: str, optional, default is None The date to fetch reports after in YYYY-MM-DD format
            before: str, optional, default is None The date to fetch reports before in YYYY-MM-DD format
        Returns:
            str: Properly formatted JSON string of reports list
        """
        after_ts = None
        before_ts = None
    
        if after:
            after_ts = datetime.strptime(after, "%Y-%m-%d").timestamp()
    
        if before:
            before_ts = datetime.strptime(before, "%Y-%m-%d").timestamp()
    
        reports = await gb_client.get_reports(
            standup_id=standup_id,
            user_id=user_id,
            after=after_ts,
            before=before_ts,
        )
        parsed_reports = [report_from_json_response(r) for r in reports]
        parsed_reports_json = [r.model_dump() for r in parsed_reports]
        unique_reporters = list({r.reporter for r in parsed_reports})
        return [
            types.TextContent(
                type="text",
                text=json.dumps(
                    {
                        "number_of_reports": len(parsed_reports),
                        "reports": parsed_reports_json,
                        "number_of_reporters": len(unique_reporters),
                    }
                ),
            )
        ]
  • The tool definition/schema with name 'fetch_reports', description, and input schema specifying optional parameters: standup_id, user_id, after, before.
    fetch_reports = types.Tool(
        name="fetch_reports",
        description="Retrieves Geekbot standup reports. Use this tool to analyze team updates or updates from specific colleagues, track progress, or compile summaries of standup activities. This tool is usually used after the `list_standups` tool.",
        inputSchema={
            "type": "object",
            "properties": {
                "standup_id": {
                    "type": "integer",
                    "description": "ID of the specific standup to fetch reports for. If not provided, reports for all standups will be fetched.",
                },
                "user_id": {
                    "type": "string",
                    "description": "ID of the specific user to fetch reports for. If not provided, reports for all members will be fetched.",
                },
                "after": {
                    "type": "string",
                    "description": "Fetch reports after this date (format: YYYY-MM-DD)",
                },
                "before": {
                    "type": "string",
                    "description": "Fetch reports before this date (format: YYYY-MM-DD)",
                },
            },
            "required": [],
        },
    )
  • Registration of fetch_reports in the tools list (line 19) so it is discoverable via list_tools().
    def list_tools() -> list[types.Tool]:
        return [
            list_members,
            list_standups,
            fetch_reports,
            post_report,
            list_polls,
            fetch_poll_results,
        ]
  • The run_tool routing/dispatch that matches the string 'fetch_reports' and calls handle_fetch_reports with the client and arguments.
    async def run_tool(
        gb_client: GeekbotClient,
        name: str,
        arguments: dict[str, str] | None,
    ) -> list[types.TextContent | types.ImageContent | types.EmbeddedResource]:
        match name:
            case "list_members":
                return await handle_list_members(gb_client)
            case "list_standups":
                return await handle_list_standups(gb_client)
            case "fetch_reports":
                return await handle_fetch_reports(gb_client, **arguments)
            case "post_report":
                return await handle_post_report(gb_client, **arguments)
            case "list_polls":
                return await handle_list_polls(gb_client)
            case "fetch_poll_results":
                return await handle_fetch_poll_results(gb_client, **arguments)
            case _:
                raise ValueError(f"Tool {name} not found")
  • Prompt template that references fetch_reports tool in its workflow instructions for generating weekly rollup reports.
    weekly_rollup_report_prompt = types.Prompt(
        name="weekly_rollup_report",
        description="Generate a comprehensive weekly rollup report that summarizes team standup responses, highlights key updates, identifies risks and mitigation strategies, outlines next steps, and tracks upcoming launches. The report organizes information in a structured format for executive visibility and team alignment.",
        arguments=[
            types.PromptArgument(
                name="standup_id",
                description="The ID of the standup to include in the rollup report",
                required=False,
            ),
        ],
    )
Behavior2/5

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

No annotations are provided, so the description must fully disclose behavioral traits. It only states 'Retrieves' without mentioning any potential issues like large result sets if no filters are applied, authentication requirements, or rate limits.

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 very concise with two sentences. The first sentence states the core purpose, and the second provides context on usage and ordering. No unnecessary information.

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 has 4 optional parameters and no output schema, the description adequately covers purpose and usage hint but lacks behavioral details (e.g., default behavior when no filters are set). It is minimally sufficient but not comprehensive.

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 input schema has 100% description coverage for all 4 parameters. The description does not add any additional meaning beyond the schema, so it meets the baseline without adding value.

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 tool retrieves Geekbot standup reports, uses specific verbs, and provides use cases like analyzing team updates. It distinguishes from siblings by mentioning it is used after list_standups, differentiating it from fetch_poll_results.

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

Usage Guidelines4/5

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

The description explains when to use the tool (to analyze standup reports) and suggests it is typically used after list_standups. However, it does not explicitly state when not to use it or mention alternatives like fetch_poll_results.

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