Skip to main content
Glama

list_polls

Retrieves all Geekbot polls a user has access to, with complete configuration: name, time, questions, participants, recurrence, anonymity.

Instructions

Retrieves and displays all Geekbot polls a user has access to, including their complete configuration details such as name, time, timezone, questions, participants, recurrence, anonymous, and creator.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function that executes the list_polls tool logic. It calls gb.get_polls(), parses the response using poll_from_json_response, and returns a formatted JSON with the number of polls and their details.
    async def handle_list_polls(gb: GeekbotClient) -> list[types.TextContent]:
        """List all polls of a Geekbot user
    
        Returns:
            str: Properly formatted JSON string of polls list
        """
        polls = await gb.get_polls()
        parsed_polls = [poll_from_json_response(p).model_dump() for p in polls]
        return [
            types.TextContent(
                type="text",
                text=json.dumps(
                    {
                        "number_of_polls": len(parsed_polls),
                        "polls": parsed_polls,
                    }
                ),
            )
        ]
  • The Tool definition including name 'list_polls', description, and inputSchema (empty object, no parameters required).
    list_polls = types.Tool(
        name="list_polls",
        description="Retrieves and displays all Geekbot polls a user has access to, including their complete configuration details such as name, time, timezone, questions, participants, recurrence, anonymous, and creator.",
        inputSchema={"type": "object", "properties": {}, "required": []},
    )
  • Import of handle_list_polls and list_polls from the list_polls module.
    from geekbot_mcp.tools.list_polls import handle_list_polls, list_polls
  • Registration of list_polls in the list_tools() function which returns all available tools.
    list_polls,
  • The run_tool function dispatches to handle_list_polls when the tool name is 'list_polls'.
    case "list_polls":
        return await handle_list_polls(gb_client)
Behavior3/5

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

With no annotations provided, the description bears the full burden. It indicates a read operation ('Retrieves and displays'), but lacks details on side effects, pagination, or error handling. The description is adequate for a simple list but not rich.

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 well-formed sentence that front-loads the purpose and includes key details. Every word earns its place; no unnecessary content.

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 parameters and no output schema, the description lists the fields returned, which is sufficient for understanding what the tool does. It does not cover error scenarios, but for a simple list tool, it is complete enough.

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?

The input schema has no parameters (100% coverage vacuously). The description adds meaning by enumerating the configuration fields returned (name, time, timezone, etc.), which is helpful beyond the empty schema. A baseline of 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 the verb 'Retrieves and displays' and the resource 'all Geekbot polls a user has access to', with specific fields listed (name, time, etc.). It distinguishes from siblings like fetch_poll_results and list_standups.

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 implies that this tool is for listing polls, but it does not explicitly state when to use it over alternatives (e.g., fetch_poll_results, list_standups) or any prerequisites (e.g., user authentication). It provides clear context but no exclusions.

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