Skip to main content
Glama
njoerd114

kubecon-eu-mcp

by njoerd114
OverviewSchemaRelated ServersScoreDiscussions
Python

get_hotel_info

Retrieve hotel block details for KubeCon Europe 2026, including rates, distances to the venue, and availability to help attendees plan their stay.

Instructions

Get conference hotel block information with rates and distances.

Returns: JSON array of hotels with name, address, rate, distance to venue, and availability.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • src/kubecon_eu_mcp/server.py:210-217 (handler)
    The handler function for the `get_hotel_info` tool.
    async def get_hotel_info() -> str:
    """Get conference hotel block information with rates and distances.

    Returns:
        JSON array of hotels with name, address, rate, distance to venue, and availability.
    """
    hotels = data_service.get_hotels()
    return json.dumps([h.to_dict() for h in hotels], indent=2)
  • src/kubecon_eu_mcp/server.py:209-209 (registration)
    Registration of the `get_hotel_info` tool using the `@mcp.tool()` decorator.
    @mcp.tool()

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 mentions the return format ('JSON array of hotels with name, address, rate, distance to venue, and availability'), which is helpful, but lacks details on permissions, rate limits, error handling, or whether it's a read-only operation. For a tool with zero annotation coverage, 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 core purpose and the second detailing the return format. Both sentences earn their place by providing essential information without redundancy. It could be slightly improved by integrating the return details more seamlessly, but it's 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 has 0 parameters, 100% schema coverage, and an output schema exists, the description is adequate but minimal. It covers the purpose and return format, which aligns with the output schema's role. However, without annotations, it misses behavioral context like safety or constraints, making it only partially complete for effective agent use.

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 are no parameters to document. The description doesn't need to add parameter semantics, and it appropriately focuses on the output. A baseline score of 4 is given as it handles the lack of parameters well without introducing confusion.

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 conference hotel block information with rates and distances.' It specifies the verb ('Get') and resource ('conference hotel block information'), making it easy to understand what the tool does. However, it doesn't explicitly differentiate from sibling tools like 'get_travel_info' or 'get_venue_info', which might also involve travel-related information.

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 any prerequisites, context for usage, or comparisons to sibling tools such as 'get_travel_info' or 'get_venue_info'. Users must infer usage based on the tool name and description 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