Skip to main content
Glama
njoerd114

kubecon-eu-mcp

by njoerd114

find_speaker

Search KubeCon Europe 2026 sessions by speaker name to find presentations matching specific presenters.

Instructions

Find sessions by a specific speaker.

Args: name: Speaker name or partial name (e.g., "Lin Sun", "Bryce").

Returns: JSON array of sessions featuring the speaker.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The handler function 'find_speaker' decorated with @mcp.tool() that invokes the data service to search for speakers.
    @mcp.tool()
    async def find_speaker(name: str) -> str:
        """Find sessions by a specific speaker.
    
        Args:
            name: Speaker name or partial name (e.g., "Lin Sun", "Bryce").
    
        Returns:
            JSON array of sessions featuring the speaker.
        """
        results = await data_service.find_speakers(name)
        if not results:
            return json.dumps(
                {
                    "message": f"No sessions found for speaker '{name}'.",
                    "suggestion": "Try a partial name or check spelling.",
                }
            )
        return json.dumps([s.to_dict() for s in results], indent=2)
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the tool returns a 'JSON array of sessions featuring the speaker,' which adds some context about output format. However, it lacks details on permissions, rate limits, error handling, or whether it's a read-only operation, leaving significant gaps 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 well-structured and concise, with a clear purpose statement followed by 'Args:' and 'Returns:' sections. Each sentence adds value without redundancy, making it easy to parse and front-loaded with essential information. No wasted words are present.

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 moderate complexity (one parameter, no annotations, but with an output schema), the description is adequate but has clear gaps. It covers the purpose and parameter semantics well, and the output schema likely details return values, reducing the need for that in the description. However, it lacks usage guidelines and behavioral context, making it incomplete for optimal 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 description adds meaningful semantics beyond the input schema, which has 0% description coverage. It explains that the 'name' parameter accepts 'Speaker name or partial name (e.g., "Lin Sun", "Bryce"),' clarifying usage with examples. Since there's only one parameter and the schema provides no descriptions, this compensation is effective, though not exhaustive.

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: 'Find sessions by a specific speaker.' It specifies the verb ('Find') and resource ('sessions'), and distinguishes it from siblings like 'search_sessions' by focusing on speaker-based filtering. However, it doesn't explicitly contrast with all siblings (e.g., 'get_schedule'), keeping it from a perfect score.

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 when to choose 'find_speaker' over 'search_sessions' or 'get_schedule', nor does it specify prerequisites or exclusions. This lack of contextual direction limits its utility for an AI agent.

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