Skip to main content
Glama
jupiterbak

AYX-MCP-Wrapper

by jupiterbak

lookup_connection

Retrieve DCM Connection details used in Alteryx workflows by providing the connection identifier. This tool helps users access connection configurations for workflow management.

Instructions

Lookup a DCM Connection as referenced in workflows

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
connection_idYes

Implementation Reference

  • The main handler function in the Tools class that performs the actual API call to lookup the DCM connection using the provided connection_id and returns a pretty-formatted response or error.
    def lookup_connection(self, connection_id: str):
        """Lookup a DCM Connection as referenced in workflows"""
        try:
            api_response = self.dcm_api.d_cme_lookup_dcm_connection(connection_id)
            return pprint.pformat(api_response)
        except ApiException as e:
            return f"Error: {e}"
  • MCP tool registration decorator and wrapper function in MCPServer that delegates the call to the underlying tools instance's lookup_connection method.
    @self.app.tool()
    def lookup_connection(connection_id: str):
        """Lookup a DCM Connection as referenced in workflows"""
        return self.tools.lookup_connection(connection_id)
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 of behavioral disclosure. It states 'Lookup', implying a read operation, but does not address permissions, rate limits, error handling, or what the output entails (e.g., connection details). This leaves significant gaps for a tool with no annotation coverage.

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 with no wasted words, making it appropriately sized and front-loaded. It directly states the tool's purpose without unnecessary elaboration, earning full marks for conciseness.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given no annotations, no output schema, and low parameter coverage, the description is incomplete. It lacks details on behavioral traits, parameter usage, and return values, making it inadequate for a tool that likely retrieves specific data, especially compared to sibling tools with similar functions.

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

Parameters2/5

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

The input schema has 1 parameter with 0% description coverage, and the tool description does not explain the 'connection_id' parameter's meaning, format, or source (e.g., from workflows). With low schema coverage, the description fails to compensate by adding semantic details beyond the basic mention of 'DCM Connection'.

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

Purpose3/5

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

The description states the tool 'Lookup a DCM Connection as referenced in workflows', which specifies the verb 'Lookup' and resource 'DCM Connection', providing a clear basic purpose. However, it lacks differentiation from sibling tools like 'get_connection_by_id', making the scope vague regarding how it differs from other retrieval tools.

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?

The description offers no guidance on when to use this tool versus alternatives such as 'get_connection_by_id' or other sibling tools. It mentions 'as referenced in workflows', which implies a context but does not specify prerequisites, exclusions, or explicit alternatives, 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/jupiterbak/AYX-MCP-Wrapper'

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