Skip to main content
Glama
alaturqua

MCP Trino Server

by alaturqua

show_create_view

Retrieve the CREATE VIEW statement for a view using its catalog, schema, and name.

Instructions

Show the CREATE VIEW statement for a specific view

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
catalogYescatalog name
schema_nameYesschema name
viewYesThe name of the view

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • MCP tool handler function that decorates show_create_view with @mcp.tool and calls client.show_create_view().
    @mcp.tool(description="Show the CREATE VIEW statement for a specific view")
    def show_create_view(
        catalog: str = Field(description="catalog name "),
        schema_name: str = Field(description="schema name "),
        view: str = Field(description="The name of the view"),
    ) -> str:
        """Show the CREATE VIEW statement for a view.
    
        Args:
            catalog: catalog name
            schema_name:  schema name
            view: The name of the view
    
        Returns:
            str: The CREATE VIEW statement
        """
        return client.show_create_view(catalog, schema_name, view)
  • Client implementation that builds and executes the SQL 'SHOW CREATE VIEW' query and returns the result.
    def show_create_view(
        self,
        catalog: str,
        schema: str,
        view: str,
    ) -> str:
        """Show the CREATE VIEW statement for a view.
    
        Args:
            catalog (str): The catalog name. If None, uses configured default.
            schema (str): The schema name. If None, uses configured default.
            view (str): The name of the view.
    
        Returns:
            str: The CREATE VIEW statement for the specified view.
    
        Raises:
            CatalogSchemaError: If either catalog or schema is not specified and not configured.
        """
        catalog = catalog or self.config.catalog
        schema = schema or self.config.schema
        if not catalog or not schema:
            raise CatalogSchemaError
        query = f"SHOW CREATE VIEW {catalog}.{schema}.{view}"
        result = json.loads(self.execute_query(query))
        return result[0]["Create View"] if result else ""
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 only states the function and does not mention that it is read-only, any required permissions, rate limits, or side effects.

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 is appropriately front-loaded but could benefit from slightly more detail.

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 presence of an output schema, the description need not explain return values. However, it lacks example usage or differentiation from sibling tools like 'show_create_table', making it minimally complete.

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

Parameters3/5

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

The input schema has 100% description coverage, so the schema already documents parameters. The tool description adds no extra meaning beyond the schema, hitting the baseline of 3.

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 clearly states the verb 'show', the resource 'CREATE VIEW statement', and the target 'specific view'. It distinguishes the tool from siblings like 'show_create_table' and 'describe_table'.

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 alternatives is provided. It does not mention when not to use it or suggest alternative tools for different scenarios.

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