Skip to main content
Glama
timeplus-io

mcp-timeplus

by timeplus-io

connect_to_apache_iceberg

Create a Timeplus database in Iceberg type to connect to Apache Iceberg using an AWS account, S3 bucket, and region.

Instructions

Create a Timeplus database in iceberg type to connect to Iceberg

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
iceberg_dbYes
aws_account_idYes
s3_bucketYes
aws_regionNous-west-2
is_s3_table_bucketNo

Implementation Reference

  • The `connect_to_apache_iceberg` function is the handler decorated with @mcp.tool(). It creates a Timeplus database of type 'iceberg' configured to connect to Apache Iceberg via AWS Glue catalog and S3 storage, then shows the streams in that database.
    @mcp.tool()
    def connect_to_apache_iceberg(iceberg_db: str,aws_account_id: int, s3_bucket: str, aws_region: str="us-west-2",is_s3_table_bucket: bool=False):
        """Create a Timeplus database in iceberg type to connect to Iceberg"""
        if iceberg_db is None or aws_account_id is None or s3_bucket is None:
            return {"error": "iceberg_db, aws_account_id, and s3_bucket are required"}
        logger.info("Creating Iceberg database")
        warehouse=aws_account_id
        storage_endpoint=f"https://{s3_bucket}.s3.{aws_region}.amazonaws.com"
        if is_s3_table_bucket:
            warehouse=f"{aws_account_id}:s3tablescatalog/{s3_bucket}"
            storage_endpoint=f"https://s3tables.{aws_region}.amazonaws.com/{s3_bucket}"
    
        sql=f"""CREATE DATABASE {iceberg_db}
                SETTINGS type='iceberg',catalog_uri='https://glue.{aws_region}.amazonaws.com/iceberg',catalog_type='rest',
                        warehouse='{warehouse}',storage_endpoint='{storage_endpoint}',use_environment_credentials=true,
                        rest_catalog_sigv4_enabled=true,rest_catalog_signing_region='{aws_region}',rest_catalog_signing_name='glue'
        """
        run_sql(sql)
        logger.info("Iceberg database created")
    
        sql=f"SHOW STREAMS FROM {iceberg_db}"
        return run_sql(sql)
  • The FastMCP server is instantiated, and the @mcp.tool() decorator on line 242 registers 'connect_to_apache_iceberg' as an MCP tool.
    mcp = FastMCP(MCP_SERVER_NAME, dependencies=deps)
  • The function is imported and exposed in the package's __init__.py.
    connect_to_apache_iceberg,
  • The function name is listed in __all__ for public export.
    "connect_to_apache_iceberg",
Behavior1/5

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

No annotations provided, and the description does not disclose side effects, idempotency, or required permissions. Simply stating 'create' without behavioral context is insufficient.

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

Conciseness3/5

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

The description is a single sentence, making it concise, but it lacks structure or any additional useful details. It is under-specified rather than effectively concise.

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?

With 0% schema coverage, no annotations, and no output schema, the description fails to provide enough context for correct invocation. Critical details about parameters and behavior are missing.

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?

Schema description coverage is 0%, and the description adds no information about any of the 5 parameters. The agent must rely solely on parameter names, which are ambiguous (e.g., 'aws_account_id' may not be self-explanatory).

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 action 'Create a Timeplus database' and the target 'to connect to Iceberg'. The verb and resource are specific, and it differentiates from sibling tools focused on Kafka or general SQL.

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 on when to use this tool vs. alternatives, no prerequisites or conditions mentioned.

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