Skip to main content
Glama
jupiterbak

AYX-MCP-Wrapper

by jupiterbak

get_credential_by_id

Retrieve credential details by ID to access stored authentication information in Alteryx Server for workflow management and data integration tasks.

Instructions

Get the details of an existing credential

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
credential_idYes

Implementation Reference

  • The core handler function that executes the tool logic by calling the Alteryx credentials API to retrieve the credential details by ID and formatting the response with pprint.
    def get_credential_by_id(self, credential_id: str):
        """Get the details of an existing credential."""
        try:
            api_response = self.credentials_api.credentials_get_credential(credential_id)
            return pprint.pformat(api_response)
        except ApiException as e:
            return f"Error: {e}"
  • Registers the get_credential_by_id tool with the MCP server using the @app.tool() decorator, which delegates execution to the handler in the tools class.
    @self.app.tool()
    def get_credential_by_id(credential_id: str):
        """Get the details of an existing credential"""
        return self.tools.get_credential_by_id(credential_id)
Behavior2/5

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

No annotations are provided, so the description carries full burden. It states 'Get the details' which implies a read operation, but doesn't disclose behavioral traits such as authentication requirements, rate limits, error handling, or what 'details' include. For a tool with zero annotation coverage, this leaves significant gaps in understanding how it behaves beyond basic purpose.

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 that front-loads the core action without unnecessary words. It's appropriately sized for a simple retrieval tool, with zero waste or redundancy, making it easy to parse quickly.

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 the tool's simplicity (1 parameter, no output schema), the description is incomplete. It lacks details on what 'details' include, error cases, or behavioral context, which are crucial for effective use. Without annotations or output schema, the description should provide more context to compensate, but it does not.

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?

Schema description coverage is 0%, with one parameter 'credential_id' undocumented in the schema. The description adds no meaning beyond what the schema provides—it doesn't explain what a credential ID is, its format, or where to find it. With low coverage and no compensatory details, the description fails to clarify parameter semantics adequately.

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

Purpose4/5

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

The description clearly states the verb 'Get' and the resource 'details of an existing credential', making the purpose understandable. It distinguishes from siblings like 'get_all_credentials' by specifying retrieval by ID, though it doesn't explicitly name alternatives. The purpose is specific enough for basic understanding but lacks explicit sibling differentiation.

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 provides no guidance on when to use this tool versus alternatives like 'get_all_credentials' or other 'get_by_id' siblings. It mentions 'existing credential' but doesn't specify prerequisites or exclusions, leaving usage context implied rather than explicit. No alternatives or when-not scenarios are addressed.

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