Skip to main content
Glama
timeplus-io

mcp-timeplus

by timeplus-io

list_kafka_topics

List Kafka topics available through the Timeplus integration for streaming data.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function for the 'list_kafka_topics' tool. Uses confluent_kafka AdminClient to list all topics in the Kafka cluster and returns topic names with partition counts.
    @mcp.tool()
    def list_kafka_topics():
        logger.info("Listing all topics in the Kafka cluster")
        admin_client = AdminClient(json.loads(os.environ['TIMEPLUS_KAFKA_CONFIG']))
        topics = admin_client.list_topics(timeout=10).topics
        topics_array = []
        for topic, detail in topics.items():
            topic_info = {"topic": topic, "partitions": len(detail.partitions)}
            topics_array.append(topic_info)
        return topics_array
  • The tool is registered as an MCP tool via the @mcp.tool() decorator on line 171.
    @mcp.tool()
  • The function has no parameters - this tool takes no input arguments. Its return type is a list of dicts with 'topic' and 'partitions' keys.
    @mcp.tool()
  • The TIMEPLUS_KAFKA_CONFIG environment variable (used by the handler) is not defined in mcp_env.py but is expected to be set externally. This config class handles other Timeplus env vars.
    """Environment configuration for the MCP Timeplus server.
    
    This module handles all environment variable configuration with sensible defaults
    and type conversion.
    """
    
    from dataclasses import dataclass
    import os
    from typing import Optional
    
    
    @dataclass
    class TimeplusConfig:
  • The function is re-exported from the package's __init__.py, making it part of the public API.
    from .mcp_server import (
        create_timeplus_client,
        list_databases,
        list_tables,
        run_sql,
        list_kafka_topics,
        explore_kafka_topic,
Behavior1/5

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

Tool has no description.

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

Conciseness1/5

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

Tool has no description.

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

Completeness1/5

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

Tool has no description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Tool has no description.

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/timeplus-io/mcp-timeplus'

If you have feedback or need assistance with the MCP directory API, please join our Discord server