Skip to main content
Glama
njoerd114

kubecon-eu-mcp

by njoerd114

get_colocated_events

Retrieve co-located events for Monday at KubeCon Europe 2026, including ArgoCon and CiliumCon, with details on duration, room locations, and requirements.

Instructions

Get Monday's co-located events (ArgoCon, CiliumCon, Agentics Day, etc.).

Returns: JSON array of co-located events with name, duration, room, and requirements.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The MCP tool handler function 'get_colocated_events' which returns JSON data of Monday's co-located events.
    @mcp.tool()
    async def get_colocated_events() -> str:
        """Get Monday's co-located events (ArgoCon, CiliumCon, Agentics Day, etc.).
    
        Returns:
            JSON array of co-located events with name, duration, room, and requirements.
        """
        events = data_service.get_colocated_events()
        return json.dumps([e.to_dict() for e in events], indent=2)
  • Data service method that provides the underlying co-located events data.
    def get_colocated_events(self) -> list[ColocatedEvent]:
        return COLOCATED_EVENTS
Behavior2/5

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

No annotations are provided, so the description carries full burden. It mentions the return format (JSON array with fields like name, duration) but lacks critical behavioral details: whether this is a read-only operation, if it requires authentication, rate limits, error conditions, or how it handles empty results. The description adds minimal context beyond basic output structure.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is appropriately sized and front-loaded: the first sentence states the purpose clearly, and the second provides output details. There's no wasted text, though it could be slightly more structured (e.g., bullet points for return fields). Every sentence earns its place.

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

Completeness3/5

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

Given the tool has no parameters, an output schema exists (implied by 'Returns'), and no annotations, the description is moderately complete. It covers purpose and output format but lacks behavioral context (e.g., safety, errors) and usage guidelines. For a simple read tool, this is adequate but has clear gaps in transparency.

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 0 parameters with 100% schema description coverage (empty schema). The description doesn't need to explain parameters, so it appropriately focuses on output. It adds value by specifying the return data structure (JSON array with name, duration, room, requirements), which compensates for the lack of parameter details.

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: 'Get Monday's co-located events' with specific examples (ArgoCon, CiliumCon, Agentics Day). It distinguishes from siblings like 'get_schedule' or 'search_sessions' by focusing specifically on co-located events rather than general sessions. However, it doesn't explicitly differentiate from all siblings (e.g., 'find_parties' might overlap).

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 provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites, context (e.g., only for Monday events), or when to choose siblings like 'get_schedule' for broader scheduling or 'search_sessions' for filtered queries. Usage is implied but not explicitly stated.

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