Skip to main content
Glama
ryft-io

IcebergMCP

by ryft-io

get_namespaces

Retrieve available namespaces from the Iceberg catalog to organize and access data lakehouse tables efficiently.

Instructions

Provides a list of namespaces from the Iceberg catalog.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The main handler function for the 'get_namespaces' tool. It uses the get_catalog helper to list namespaces from the GlueCatalog and returns them as a newline-separated string. The @mcp.tool() decorator registers the tool with the MCP server.
    @mcp.tool()
    def get_namespaces() -> str:
        """Provides a list of namespaces from the Iceberg catalog."""
        catalog = get_catalog()
        namespaces = catalog.list_namespaces()
        return "\n".join(ns[0] for ns in namespaces)
  • Helper function to initialize the Iceberg GlueCatalog using AWS credentials obtained via boto3 session with profile from config and specified region.
    def get_catalog() -> GlueCatalog:
        try:
            session = boto3.Session(profile_name=iceberg_config.profile_name)
            credentials = session.get_credentials().get_frozen_credentials()
    
            catalog = GlueCatalog(
                "glue",
                **{
                    "client.access-key-id": credentials.access_key,
                    "client.secret-access-key": credentials.secret_key,
                    "client.session-token": credentials.token,
                    "client.region": iceberg_config.region,
                },
            )
        except Exception as e:
            logger.error(f"Error creating AWS connection: {str(e)}")
            raise
        return catalog
  • Configuration values for AWS profile and region used by get_catalog to create the catalog instance.
    profile_name = os.environ.get("ICEBERG_MCP_PROFILE")
    region = os.environ.get("ICEBERG_AWS_REGION") or 'us-east-1'
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 provides a list, implying a read-only operation, but lacks details on permissions, rate limits, pagination, or error behavior. For a tool with zero annotation coverage, this is a significant gap in behavioral disclosure.

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 a single, efficient sentence that directly states the tool's function without any wasted words. It is front-loaded with the core purpose, making it highly concise and well-structured.

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 simplicity (0 parameters, no output schema, no annotations), the description is adequate but minimal. It covers the basic purpose but lacks context about the Iceberg catalog, return format, or usage scenarios, leaving gaps for an agent to infer behavior.

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 input schema has 0 parameters with 100% coverage, so no parameter documentation is needed. The description appropriately doesn't discuss parameters, earning a baseline score of 4 for not adding unnecessary information beyond the schema.

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 verb ('Provides') and resource ('list of namespaces from the Iceberg catalog'), making the purpose understandable. It doesn't explicitly differentiate from sibling tools like 'get_iceberg_tables' or 'get_table_schema', but the resource specificity (namespaces vs tables/partitions/properties/schema) provides implicit distinction.

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 explicit guidance is provided on when to use this tool versus alternatives. The description implies it's for retrieving namespaces, but it doesn't mention prerequisites, context (e.g., before accessing tables), or comparisons to sibling tools like 'get_iceberg_tables' for related data.

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

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