Skip to main content
Glama
abutbul

Gatherings MCP Server

by abutbul

list_gatherings

Retrieve all social events tracked for expense management and reimbursement calculations between friends.

Instructions

List all gatherings

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • src/index.ts:176-183 (registration)
    Registration of the 'list_gatherings' tool including name, description, and empty input schema in the MCP server's ListTools response.
    {
      name: 'list_gatherings',
      description: 'List all gatherings',
      inputSchema: {
        type: 'object',
        properties: {},
      },
    },
  • MCP tool handler case that constructs the CLI command to execute the Python script with 'list' subcommand.
    command += ' list';
    break;
  • CLI handler for the 'list' command invoked by the MCP server, which fetches gatherings and outputs the list in JSON or human-readable format.
    def handle_list(service, args):
        """Handle the list command."""
        try:
            gatherings = service.list_gatherings()
            result = {
                "success": True,
                "gatherings": [
                    {
                        "id": g.id,
                        "status": g.status.value
                    }
                    for g in gatherings
                ] if gatherings else []
            }
            
            if args.json:
                print(json.dumps(result))
            else:
                if not gatherings:
                    print("No gatherings found")
                else:
                    print(f"Found {len(gatherings)} gatherings:")
                    for gathering in gatherings:
                        print(f"  {gathering.id} - Status: {gathering.status.value}")
            return True
        except ValueError as e:
            error = {"success": False, "error": str(e)}
            if args.json:
                print(json.dumps(error))
            else:
                print(f"Error: {e}")
            return False
  • GatheringService method that delegates listing of gatherings to the DatabaseManager.
    def list_gatherings(self) -> List[Gathering]:
        """
        List all gatherings.
        
        Returns:
            A list of all Gathering objects
        """
        return self.db_manager.list_gatherings()
  • DatabaseManager method that queries the database for all Gathering records, implementing the core data retrieval logic.
    def list_gatherings(self) -> List[Gathering]:
        """
        List all gatherings.
        
        Returns:
            A list of all Gathering objects
        """
        session = self.Session()
        try:
            # Get all gatherings
            gatherings = session.query(Gathering).all()
            return gatherings
        finally:
            session.close()
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. 'List all gatherings' implies a read-only operation, but it doesn't specify aspects like pagination, sorting, filtering, or error handling. For a tool with zero annotation coverage, this is a significant gap in transparency.

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 extremely concise with 'List all gatherings', a single phrase that front-loads the core action. There is no wasted language, making it efficient and easy to parse, though this conciseness comes at the cost of detail.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the lack of annotations and output schema, the description is incomplete. It doesn't explain what 'gatherings' are, the return format, or behavioral traits. For a tool in a set with siblings like 'show_gathering', more context is needed to distinguish usage and understand output.

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 0 parameters with 100% coverage, meaning there are no parameters to document. The description doesn't need to add parameter semantics, so it meets the baseline of 4 for tools with no parameters, as it doesn't mislead or omit necessary information.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'List all gatherings' clearly states the verb ('List') and resource ('gatherings'), providing basic purpose. However, it lacks specificity about what 'gatherings' are in this context and doesn't differentiate from sibling tools like 'show_gathering' or 'create_gathering', making it somewhat vague.

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 offers no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites, context, or exclusions, such as whether it's for viewing all gatherings versus specific ones (e.g., 'show_gathering' for details). This leaves the agent with minimal usage direction.

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/abutbul/gatherings-mcp'

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