Skip to main content
Glama
blitzstermayank

Teradata MCP Server

tmpl_nameOfTool

Analyze arguments to generate formatted query results with metadata for Teradata database operations.

Instructions

Arguments: arguments - arguments to analyze

Returns: ResponseType: formatted response with query results + metadata

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
argumentYes

Implementation Reference

  • The handler function that implements the core logic of the 'tmpl_nameOfTool' MCP tool. It takes a Teradata connection and an optional string argument, executes a placeholder SQL query, formats the results, and returns a response with metadata.
    def handle_tmpl_nameOfTool(conn: TeradataConnection, argument: str | None, *args, **kwargs):
        """
        <description of what the tool is for>
    
        Arguments:
          arguments - arguments to analyze
    
        Returns:
          ResponseType: formatted response with query results + metadata
        """
        logger.debug(f"Tool: handle_tmpl_nameOfTool: Args: argument: {argument}")
    
        with conn.cursor() as cur:
            if argument == "":
                logger.debug("No argument provided")
                rows = cur.execute("Teradata query goes here;")
            else:
                logger.debug(f"Argument provided: {argument}")
                rows = cur.execute(f"Teradata query goes here with argument {argument};")
            data = rows_to_json(cur.description, rows.fetchall())
            metadata = {
                "tool_name": "tmpl_nameOfTool",
                "argument": argument,
                "rows": len(data)
            }
            logger.debug(f"Tool: handle_tmpl_nameOfTool: metadata: {metadata}")
            return create_response(data, metadata)
Behavior1/5

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

No annotations are provided, and the description offers no behavioral details such as whether it's read-only, destructive, requires authentication, or has rate limits. It fails to disclose any traits beyond the placeholder text.

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

Conciseness2/5

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

The description is structured with placeholders but is under-specified, not concise. It includes unnecessary boilerplate (e.g., 'Arguments:', 'Returns:') without substantive content, wasting space rather than being efficiently informative.

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?

Given the lack of annotations, 0% schema coverage, no output schema, and a placeholder description, the tool is completely inadequate for understanding. It fails to provide necessary context for a tool with one required parameter among many siblings.

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 does not explain the 'argument' parameter's purpose, format, or constraints. It merely repeats the parameter name without adding meaningful semantics, leaving it undocumented.

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?

The description is a placeholder ('<description of what the tool is for>') that does not state what the tool does, making it tautological and indistinguishable from siblings. It provides no specific verb or resource, failing to clarify its purpose.

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?

No guidance is provided on when to use this tool versus alternatives among the many sibling tools listed. The description lacks any context, prerequisites, or exclusions, leaving usage unclear.

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/blitzstermayank/MCP'

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