Skip to main content
Glama
jupiterbak

AYX-MCP-Wrapper

by jupiterbak

get_connection_by_id

Retrieve specific connection details from Alteryx Servers using its unique identifier to access configuration and status information.

Instructions

Get a connection by its ID

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
connection_idYes

Implementation Reference

  • Core implementation of the get_connection_by_id tool. Fetches the connection details from the DCM API using the provided connection_id and returns a pretty-formatted string of the API response or an error message.
    def get_connection_by_id(self, connection_id: str):
        """Get a connection by its ID"""
        try:
            api_response = self.dcm_api.d_cme_get_dcm_connection(connection_id)
            return pprint.pformat(api_response)
        except ApiException as e:
            return f"Error: {e}"
  • MCP tool registration decorator and wrapper function that delegates the call to the underlying tools instance method.
    @self.app.tool()
    def get_connection_by_id(connection_id: str):
        """Get a connection by its ID"""
        return self.tools.get_connection_by_id(connection_id)
  • Pydantic/Swagger-generated model defining the structure of the DCMEGetConnectionView response object returned by the underlying API, used in the tool's output.
    class DCMEGetConnectionView(object):
        """NOTE: This class is auto generated by the swagger code generator program.
    
        Do not edit the class manually.
        """
    
        """
        Attributes:
          swagger_types (dict): The key is attribute name
                                and the value is attribute type.
          attribute_map (dict): The key is attribute name
                                and the value is json key in definition.
        """
        swagger_types = {
            "shared_by": "DCMEUserView",
            "shared_from_connection": "str",
            "connection_id": "str",
            "assigned_connection_ids": "list[str]",
            "created_on": "datetime",
            "last_changed_on": "datetime",
            "owner": "DCMEUserView",
            "sharing": "DCMESharingView",
            "id": "str",
            "name": "str",
            "schema_name": "str",
            "allow_in_sdks": "bool",
            "parameters": "dict(str, object)",
            "data_source": "DCMEDataSourceView",
            "credentials": "dict(str, DCMECredentialView)",
        }
    
        attribute_map = {
            "shared_by": "sharedBy",
            "shared_from_connection": "sharedFromConnection",
            "connection_id": "connectionId",
            "assigned_connection_ids": "assignedConnectionIds",
            "created_on": "createdOn",
            "last_changed_on": "lastChangedOn",
            "owner": "owner",
            "sharing": "sharing",
            "id": "id",
            "name": "name",
            "schema_name": "schemaName",
            "allow_in_sdks": "allowInSdks",
            "parameters": "parameters",
            "data_source": "dataSource",
            "credentials": "credentials",
        }
    
        def __init__(
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It only states the basic action without mentioning whether this is a read-only operation, what permissions are required, error handling, rate limits, or what the return format looks like. For a tool with zero annotation coverage, this leaves significant behavioral questions unanswered.

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 extremely concise with just one sentence that directly states the tool's purpose. There's no wasted language or unnecessary elaboration, making it efficiently front-loaded with the core information.

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?

For a tool with no annotations, no output schema, and 0% schema description coverage, the description is inadequate. It doesn't explain what a 'connection' is in this system, what data is returned, error conditions, or how this differs from similar tools. The minimal description leaves too many contextual gaps for effective use.

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 schema has 0% description coverage for the single parameter 'connection_id', and the tool description provides no additional semantic information about what a connection ID is, its format, where to find it, or valid values. The description doesn't compensate for the complete lack of parameter documentation in the schema.

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 'Get a connection by its ID' clearly states the verb ('Get') and resource ('connection'), but it's vague about what a 'connection' represents in this context and doesn't differentiate from the sibling tool 'lookup_connection'. It provides basic purpose but lacks specificity about the domain or resource type.

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 is provided about when to use this tool versus alternatives like 'lookup_connection' or other 'get_by_id' siblings. The description offers no context about prerequisites, when this tool is appropriate, or what distinguishes it from similar tools in the server.

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