Skip to main content
Glama

fetch_reports

Retrieve standup reports from Geekbot by specifying filters such as standup ID, user ID, or date ranges. Returns a JSON-formatted list of reports for easy integration and analysis.

Instructions

Fetch reports list from Geekbot

Args:
    standup_id: int, optional, default is None The standup id to fetch reports for
    user_id: int, optional, default is None 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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
afterNo
beforeNo
standup_idNo
user_idNo

Implementation Reference

  • The fetch_reports tool is registered here in the list_tools() function which provides the tool schemas to the MCP server.
    def list_tools() -> list[types.Tool]:
        return [
            list_members,
            list_standups,
            fetch_reports,
            post_report,
            list_polls,
            fetch_poll_results,
        ]
  • Handler for the fetch_reports tool is dispatched here in the run_tool() dispatcher function.
    case "fetch_reports":
        return await handle_fetch_reports(gb_client, **arguments)
  • Core API method to fetch reports from Geekbot API. This is the underlying utility called by the fetch_reports tool handler to retrieve standup reports based on parameters like standup_id, before/after timestamps.
    async def get_reports(
        self,
        standup_id: int | None = None,
        user_id: int | None = None,
        after: int | None = None,
        before: int | None = None,
        question_ids: list | None = None,
        limit: int = 50,
    ) -> list:
        """Get list of reports"""
        endpoint = f"{self.base_url}/reports/"
    
        params = {"limit": limit}
        if standup_id:
            params["standup_id"] = standup_id
        if user_id:
            params["user_id"] = user_id
        if after:
            params["after"] = after
        if before:
            params["before"] = before
        if question_ids:
            params["question_ids"] = question_ids
    
        response = await self._client.get(endpoint, params=params)
        response.raise_for_status()
        return response.json()
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It states this is a fetch operation (implying read-only) and describes the return format, but doesn't mention authentication requirements, rate limits, pagination, error conditions, or what happens when no filters are provided. For a tool with 4 parameters and no annotation coverage, this is insufficient.

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 well-structured with clear sections (Args, Returns) and uses bullet-like formatting. It's appropriately sized for a tool with 4 parameters. Minor improvement could be made by front-loading the core purpose more prominently before parameter details.

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?

For a read operation with no output schema, the description does specify the return format (JSON string). However, with no annotations and a sibling tool present, it should provide more context about when to use this tool, authentication needs, and typical response structure. The parameter documentation is strong, but overall completeness is only adequate.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The description provides excellent parameter documentation that fully compensates for the 0% schema description coverage. It clearly explains all 4 parameters (standup_id, user_id, after, before) with their types, optional status, defaults, and format specifications (YYYY-MM-DD for dates). This adds substantial value beyond the bare schema.

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 verb ('fetch') and resource ('reports list from Geekbot'), making the purpose understandable. However, it doesn't explicitly distinguish this tool from its sibling 'fetch_standups' - both fetch operations but for different resources, which would require explicit differentiation for a score of 5.

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. There's no mention of the sibling tool 'fetch_standups' or any context about when reports versus standups should be fetched. The parameter documentation implies filtering capabilities but doesn't provide usage scenarios.

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

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