Skip to main content
Glama
njoerd114

kubecon-eu-mcp

by njoerd114

get_conference_overview

Get a quick snapshot of the conference with key details: name, dates, schedule at a glance, and useful links.

Instructions

Get a high-level overview of the entire conference.

Returns: JSON with event name, dates, schedule at a glance, and useful links.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The actual tool handler function. Decorated with @mcp.tool(), it calls data_service.get_schedule_overview() and returns the JSON result.
    @mcp.tool()
    async def get_conference_overview() -> str:
        """Get a high-level overview of the entire conference.
    
        Returns:
            JSON with event name, dates, schedule at a glance, and useful links.
        """
        overview = data_service.get_schedule_overview()
        return json.dumps(overview, indent=2)
  • The data service method that returns the schedule overview dict (delegates to static data).
    def get_schedule_overview(self) -> dict:
        return SCHEDULE_OVERVIEW
    
    def get_airline_discounts(self) -> list[dict]:
        return AIRLINE_DISCOUNTS
  • The static SCHEDULE_OVERVIEW dictionary containing the conference overview data (event name, dates, location, schedule_at_a_glance, useful_links).
    SCHEDULE_OVERVIEW = {
        "event": "KubeCon + CloudNativeCon Europe 2026",
        "dates": "23-26 March 2026",
        "location": "RAI Amsterdam, Netherlands",
        "timezone": "CET (Central European Time, UTC+1)",
        "hashtags": ["#KubeCon", "#CloudNativeCon"],
        "schedule_at_a_glance": {
            "monday": "Pre-event Programming: Co-Located Events (ArgoCon, CiliumCon, Agentics Day, Platform Engineering Day, etc.)",
            "tuesday": "Keynotes (Hall 12), Breakout Sessions, Solutions Showcase (Halls 1-5), KubeCrawl + CloudNativeFest (5:30-7PM)",
            "wednesday": "Keynotes, Breakout Sessions, Solutions Showcase",
            "thursday": "Keynotes, Breakout Sessions, Solutions Showcase",
        },
        "useful_links": {
            "schedule": "https://kccnceu2026.sched.com/",
            "colocated_schedule": "https://colocatedeventseu2026.sched.com/",
            "registration": "https://events.linuxfoundation.org/kubecon-cloudnativecon-europe/register/",
            "venue": "https://events.linuxfoundation.org/kubecon-cloudnativecon-europe/attend/venue-travel/",
            "code_of_conduct": "https://events.linuxfoundation.org/kubecon-cloudnativecon-europe/attend/code-of-conduct/",
            "youtube_recordings": "https://www.youtube.com/@cncf/playlists",
        },
    }
  • Tool registration via @mcp.tool() decorator on line 255 registers 'get_conference_overview' with FastMCP.
    @mcp.tool()
  • Test that verifies the get_conference_overview tool returns expected data structure.
    async def test_get_conference_overview():
        result = _tool_json(await mcp.call_tool("get_conference_overview", {}))
        assert result["event"] == "KubeCon + CloudNativeCon Europe 2026"
        assert "schedule_at_a_glance" in result
        assert "useful_links" in result
Behavior3/5

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

No annotations exist, so the description must handle behavioral disclosure. It states the return format (JSON with specific fields) which is helpful. However, it does not mention any authentication needs, rate limits, or potential side effects (though unlikely). It provides basic transparency but could be more explicit.

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, consisting of two short sentences. It front-loads the purpose and then lists what is returned. No unnecessary words or repetition.

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

Completeness5/5

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

Given that the tool has zero parameters and the output schema is provided (context signals indicate it exists), the description still adds value by summarizing the output fields. With low complexity, the description is fully adequate.

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 tool has no parameters, so the schema coverage is 100% by default. The description need not add parameter info, and it does not. According to guidelines, 0 parameters earns a baseline of 4, which 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 uses a specific verb ('Get') and resource ('high-level overview of the entire conference'), and lists the key content (name, dates, schedule, links). This clearly distinguishes it from sibling tools that focus on specific aspects like schedule, venue, or speakers.

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 a broad overview, but it does not explicitly state when to use it versus other tools like get_schedule or get_venue_info. No alternative tools are mentioned.

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