Skip to main content
Glama
njoerd114

kubecon-eu-mcp

by njoerd114
OverviewSchemaRelated ServersScoreDiscussions
Python

get_travel_info

Retrieve airport details, public transit information, parking options, and airline discount codes for KubeCon Europe 2026 travel planning.

Instructions

Get travel information: airport, transit, parking, and airline discounts.

Returns: JSON with airport details, public transport info, parking, and airline discount codes.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • src/kubecon_eu_mcp/server.py:220-241 (handler)
    The `get_travel_info` function is the handler that retrieves and returns venue travel information (airport, transit, parking, airline discounts) as a JSON string.
    @mcp.tool()
async def get_travel_info() -> str:
    """Get travel information: airport, transit, parking, and airline discounts.

    Returns:
        JSON with airport details, public transport info, parking, and airline discount codes.
    """
    venue = data_service.get_venue()
    return json.dumps(
        {
            "airport": {
                "name": "Amsterdam Airport Schiphol (AMS)",
                "distance": "14.4 km from venue",
                "drive_time": "~15 minutes",
                "public_transport_time": "~10 minutes by train to Amsterdam RAI station",
            },
            "public_transport": venue.transit,
            "parking": venue.parking,
            "airline_discounts": data_service.get_airline_discounts(),
        },
        indent=2,
    )

Tool Definition Quality

B3.1/5.0
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. It states the tool returns JSON with specific data types, which is helpful, but lacks critical details: it doesn't specify if this is a read-only operation, whether it requires authentication, any rate limits, or how data is sourced (e.g., real-time vs. static). For a tool with no annotations, this leaves significant gaps in understanding its behavior.

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 concise and front-loaded, with the first sentence stating the purpose and the second detailing the return format. Both sentences earn their place by providing essential information without fluff. However, the structure could be slightly improved by integrating the return details more seamlessly, but it remains efficient overall.

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's complexity (simple read operation with no parameters), the presence of an output schema reduces the need to explain return values in the description. However, with no annotations and siblings in a conference context, the description lacks context on integration (e.g., how it relates to other tools like 'get_hotel_info') and behavioral traits. It's minimally adequate but has clear gaps in usage and 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, and schema description coverage is 100%, so there's no need for parameter details in the description. The description appropriately avoids discussing inputs, focusing instead on outputs. This meets the baseline of 4 for zero-parameter tools, as it doesn't add unnecessary information beyond what the schema provides.

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 with a specific verb ('Get') and resource ('travel information'), listing the types of information retrieved (airport, transit, parking, airline discounts). It distinguishes from siblings like 'get_hotel_info' or 'get_venue_info' by focusing on travel logistics rather than accommodation or venue details. However, it doesn't explicitly differentiate from all siblings (e.g., 'get_conference_overview' might overlap in scope).

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., for conference planning), or exclusions (e.g., not for hotel booking). With siblings like 'get_hotel_info' and 'get_venue_info', there's no indication of how to choose between them, leaving the agent to infer based on tool names alone.

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