Skip to main content
Glama
alaturqua

MCP Trino Server

by alaturqua
OverviewSchemaRelated ServersScoreDiscussions
Python
Remote

show_catalogs

Retrieve a list of all available catalogs in Trino to identify data sources for querying.

Instructions

List all available catalogs

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • src/server.py:35-38 (handler)
    The MCP tool handler for 'show_catalogs'. Decorated with @mcp.tool, it delegates to client.list_catalogs().
    @mcp.tool(description="List all available catalogs")
def show_catalogs() -> str:
    """List all available catalogs."""
    return client.list_catalogs()
  • src/trino_client.py:100-107 (helper)
    The TrinoClient.list_catalogs() method that executes 'SHOW CATALOGS' query and returns newline-separated catalog names.
    def list_catalogs(self) -> str:
    """List all available catalogs.

    Returns:
        str: Newline-separated list of catalog names.
    """
    catalogs = [row["Catalog"] for row in json.loads(self.execute_query("SHOW CATALOGS"))]
    return "\n".join(catalogs)
  • src/server.py:35-35 (registration)
    The tool is registered via the @mcp.tool decorator on the show_catalogs function, with description 'List all available catalogs'.
    @mcp.tool(description="List all available catalogs")

Tool Definition Quality

B3.4/5.0
Behavior2/5

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

No annotations are provided, and the description does not disclose any behavioral traits like authentication requirements, rate limits, or whether it lists all catalogs globally or within a scope. The read-only nature is implied but not explicit.

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

Conciseness4/5

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

The description is a single, clear sentence with no wasted words. It could be slightly more explicit (e.g., 'Lists all catalogs the user has access to') but is still efficient.

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 zero parameters and an output schema, the description is adequate but minimal. It does not explain what a catalog is or provide any extra context beyond the basic action. It meets the minimum viable standard.

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?

There are no parameters, so the baseline is 4. The description does not need to add parameter information; it is sufficient.

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

Purpose5/5

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

The description 'List all available catalogs' clearly states the verb and the resource, and it distinguishes the tool from siblings like show_schemas or show_tables by specifically mentioning catalogs.

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 versus the many sibling tools, such as show_schemas or show_tables. The description does not provide context for selection.

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/alaturqua/mcp-trino-python'

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