Skip to main content
Glama
asachs01

Autotask MCP Server

autotask_test_connection

Tests the API connection to Autotask to confirm that the server can communicate with your Autotask PSA instance.

Instructions

Test Autotask API connection

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The main handler for autotask_test_connection. In the dispatch table, it calls AutotaskService.testConnection() and returns success/error.
    ['autotask_test_connection', async () => {
      const ok = await s.testConnection();
      if (!ok) {
        throw new Error('Connection to Autotask API failed. Verify AUTOTASK_USERNAME, AUTOTASK_SECRET, and AUTOTASK_INTEGRATION_CODE are configured correctly and that the API user has at least read access to Companies.');
      }
      return { result: { success: true }, message: 'Successfully connected to Autotask API' };
    }],
  • Tool definition and input schema for autotask_test_connection (name, description, empty input schema).
    {
      name: 'autotask_test_connection',
      description: 'Test Autotask API connection',
      inputSchema: {
        type: 'object',
        properties: {},
        required: []
      }
    },
  • Category registration - autotask_test_connection listed under the 'utility' category.
    export const TOOL_CATEGORIES: Record<string, { description: string; tools: string[] }> = {
      utility: {
        description: 'Connection testing and field/picklist discovery',
        tools: ['autotask_test_connection', 'autotask_list_queues', 'autotask_list_ticket_statuses', 'autotask_list_ticket_priorities', 'autotask_get_field_info']
  • The service-layer testConnection() method that performs the actual API probe via http.query.
    async testConnection(): Promise<boolean> {
      try {
        const http = await this.ensureClient();
        // Cheap probe: query Companies with a trivial filter.
        await http.query<AutotaskCompany>('Companies', MATCH_ALL, { maxRecords: 1 });
        this.logger.info('Connection test successful');
        return true;
      } catch (error) {
        this.logger.error('Connection test failed:', error);
        return false;
      }
    }
Behavior2/5

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

The description only says 'Test', which implies a non-destructive read operation, but provides no details on what the test does (e.g., authenticate, check endpoint, return status). No annotations exist to clarify behavior.

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?

Single sentence with no unnecessary words. Perfectly concise and front-loaded.

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?

For a zero-parameter tool, the description covers the basic purpose but omits expected return values, error handling, or authentication context. More detail would improve completeness without being verbose.

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

Parameters4/5

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

No parameters exist, and schema coverage is 100%. Baseline for zero parameters is 4. Description adds nothing beyond schema, which is acceptable.

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 a specific verb ('Test') and resource ('Autotask API connection'). It distinguishes from all sibling tools which perform CRUD operations on specific entities, not a general connectivity test.

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. It does not explain prerequisites, typical scenarios, or situations where testing connection is needed.

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/asachs01/autotask-mcp'

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