Skip to main content
Glama
njoerd114

kubecon-eu-mcp

by njoerd114
OverviewSchemaRelated ServersScoreDiscussions
Python

get_venue_info

Retrieve venue details including address, rooms, maps, and transit information for conference logistics planning.

Instructions

Get venue details: address, rooms, maps, and transit information.

Returns: JSON with venue name, address, room list, map links, transit info, and parking.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • src/kubecon_eu_mcp/server.py:198-206 (handler)
    The get_venue_info function is a tool decorated with @mcp.tool() that retrieves venue information using the data_service and returns it as a JSON string.
    @mcp.tool()
async def get_venue_info() -> str:
    """Get venue details: address, rooms, maps, and transit information.

    Returns:
        JSON with venue name, address, room list, map links, transit info, and parking.
    """
    venue = data_service.get_venue()
    return json.dumps(venue.to_dict(), indent=2)

Tool Definition Quality

B3.2/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. It states the tool returns JSON with specific fields, which adds some behavioral context, but lacks details on permissions, rate limits, error handling, or whether it's a read-only operation. The description doesn't contradict annotations, but it's minimal for a tool with no annotation coverage.

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 in the first sentence, followed by a clear 'Returns:' section. It's concise with no wasted words, efficiently conveying what the tool does and what it returns in two brief parts.

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, and no annotations, the description is adequate but minimal. It covers the purpose and return format, but for a tool with no behavioral annotations, it could benefit from more context like usage scenarios or limitations to be fully complete.

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 baseline for this case is 4, as the description appropriately doesn't discuss parameters and focuses on output.

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 ('venue details'), listing the types of information retrieved (address, rooms, maps, transit). It distinguishes itself from siblings like get_hotel_info or get_travel_info by focusing on venue-specific details, though it doesn't explicitly contrast them.

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?

No guidance is provided on when to use this tool versus alternatives. It doesn't mention prerequisites, context, or exclusions, such as when to choose get_venue_info over get_conference_overview or get_hotel_info for related information.

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