Skip to main content
Glama
njoerd114

kubecon-eu-mcp

by njoerd114

plan_party_route

Plan an optimized party-hopping route for KubeCon Europe evenings. Get parties sorted by time with location details to create an efficient Amsterdam itinerary based on day and preferences.

Instructions

Plan an optimized party-hopping route for an evening.

Returns parties for the requested day sorted by time, with location details to help plan an efficient route through Amsterdam.

Args: day: Day name — "monday", "tuesday", "wednesday", or "thursday". preferences: Optional preferences like "networking", "food", "near venue", "open bar".

Returns: JSON with sorted party timeline and location context for route planning.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dayYes
preferencesNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The plan_party_route tool handler, registered with @mcp.tool(), which calculates an optimized route based on party data.
    @mcp.tool()
    async def plan_party_route(day: str, preferences: str = "") -> str:
        """Plan an optimized party-hopping route for an evening.
    
        Returns parties for the requested day sorted by time, with location details
        to help plan an efficient route through Amsterdam.
    
        Args:
            day: Day name — "monday", "tuesday", "wednesday", or "thursday".
            preferences: Optional preferences like "networking", "food", "near venue", "open bar".
    
        Returns:
            JSON with sorted party timeline and location context for route planning.
        """
        parties = await data_service.get_parties_for_day(day)
        if not parties:
            return json.dumps({"message": f"No parties found for {day}."})
    
        # Sort by time (basic sort — times are like "6-9PM", "7PM-1AM")
        route = {
            "day": day,
            "total_parties": len(parties),
            "tip": (
                "Most parties near RAI Amsterdam are in the Europaplein/Zuidas area "
                "(walking distance). Parties in central Amsterdam (Keizersgracht, Amstel) "
                "are 15-25 min by tram/metro from RAI. The last metro runs around 00:30."
            ),
            "parties": [p.to_dict() for p in parties],
            "key_venues": {
                "near_rai": "Strandzuid, Amstel Boathouse, nhow Hotel, Nela Restaurant — all within 10 min walk of RAI",
                "central": "Heineken Experience, Escape DeLux, Oche — 20-25 min by tram from RAI",
                "canal_area": "Elasticsearch office (Keizersgracht) — 25 min by tram",
            },
        }
    
        return json.dumps(route, indent=2)
Behavior3/5

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

With no annotations provided, the description carries the full burden. It discloses that the tool returns sorted parties with location context for route planning, which is useful behavioral information. However, it doesn't mention potential limitations like data freshness, rate limits, or authentication requirements, leaving gaps for a tool with no annotation coverage.

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 well-structured and front-loaded with the core purpose. Each sentence adds value: the first states the purpose, the second explains the return format, and the parameter/return sections provide necessary details without redundancy. Zero waste in the text.

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 the tool's moderate complexity (2 parameters, no annotations, but with output schema), the description is reasonably complete. It explains what the tool does, parameters, and return format. The output schema existence means it doesn't need to detail return values, but it could better address behavioral aspects like error conditions or data scope.

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?

Schema description coverage is 0%, so the description must compensate. It provides meaningful semantics for both parameters: 'day' is explained with specific day name options, and 'preferences' is described with example types. This adds substantial value beyond the bare schema, though it doesn't cover all possible preference values or formats.

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 tool's purpose: 'Plan an optimized party-hopping route for an evening' and specifies it returns parties sorted by time with location details. It distinguishes from siblings like 'find_parties' by emphasizing route optimization and Amsterdam context, though it doesn't explicitly contrast with all siblings.

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 usage for evening party-hopping in Amsterdam and mentions optional preferences, but doesn't explicitly state when to use this tool versus alternatives like 'find_parties' or 'get_schedule'. It provides some context but lacks clear exclusions or named alternatives.

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/njoerd114/kubecon-eu-mcp'

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