Skip to main content
Glama
njoerd114

kubecon-eu-mcp

by njoerd114

get_schedule

Retrieve the complete conference schedule for a specific day at KubeCon + CloudNativeCon Europe 2026, returning all sessions sorted chronologically to help attendees plan their agenda.

Instructions

Get the full conference schedule for a specific day.

Args: day: Day name — "monday" (co-located), "tuesday", "wednesday", or "thursday".

Returns: JSON array of all sessions for that day, sorted by start time.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dayYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The 'get_schedule' tool handler function which calls data_service.get_schedule_for_day to retrieve sessions for a given day.
    @mcp.tool()
    async def get_schedule(day: str) -> str:
        """Get the full conference schedule for a specific day.
    
        Args:
            day: Day name — "monday" (co-located), "tuesday", "wednesday", or "thursday".
    
        Returns:
            JSON array of all sessions for that day, sorted by start time.
        """
        sessions = await data_service.get_schedule_for_day(day)
        if not sessions:
            return json.dumps(
                {
                    "message": f"No sessions found for {day}.",
                    "hint": "Valid days: monday, tuesday, wednesday, thursday",
                }
            )
        return json.dumps([s.to_dict() for s in sessions], 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 the return format (JSON array) and sorting behavior (by start time), which are useful behavioral traits. However, it does not mention potential errors, rate limits, or authentication needs, leaving some behavioral aspects unclear.

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 front-loaded with the core purpose, followed by structured sections for Args and Returns. Every sentence adds value: the first defines the tool, the second details the parameter, and the third specifies the output. No wasted words, and the structure enhances clarity.

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 the tool's low complexity (1 parameter, no nested objects), the presence of an output schema (which handles return values), and the description's thorough parameter documentation and behavioral details, it is complete enough for effective use. The description covers all necessary aspects without redundancy.

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 schema description coverage is 0%, so the description must compensate fully. It explicitly documents the single parameter 'day', including its purpose, allowed values ('monday', 'tuesday', 'wednesday', 'thursday'), and notes that 'monday' is co-located. This adds significant meaning beyond the bare schema.

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 specific action ('Get'), resource ('full conference schedule'), and scope ('for a specific day'), distinguishing it from siblings like get_conference_overview (general) or search_sessions (filtered). It precisely defines what the tool does without redundancy.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage context by specifying 'for a specific day' and lists valid day values, but does not explicitly state when to use this tool versus alternatives like search_sessions or get_colocated_events. It provides clear input constraints but lacks comparative guidance.

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