Autotask Tool Discovery

Autotask Tool Discovery & Lazy Loading

Overview

The Autotask MCP server can run in lazy loading mode, where only 4 meta-tools are exposed initially instead of all 39+ tools. This is common on remote MCP connections (e.g., Claude.ai connectors) where loading all tool schemas upfront would be expensive.

If you can see Autotask tools listed but can't call them, or if only a few Autotask tools appear — use this progressive discovery pattern.

Anti-triggers

• Authentication failures, zone errors, or malformed queries — these also present as "Autotask isn't working", but they are API problems, not discovery problems; use autotask-api-patterns.
• A tool that runs and returns an empty result — usually a filter or a picklist ID that does not exist in the tenant; use autotask-api-patterns or autotask-picklists.

Available Meta-Tools

When lazy loading is active, these 4 tools are always available:

Progressive Discovery Pattern

Step 1: List Available Categories

Tool: autotask_list_categories
Args: {}

Returns all categories:

Step 2: Get Tools for a Category

Tool: autotask_list_category_tools
Args: { "category": "time_and_billing" }

Returns full schemas for every tool in that category, including parameter names, types, descriptions, and required fields.

Step 3: Execute a Tool

Tool: autotask_execute_tool
Args: {
  "toolName": "autotask_search_resources",
  "arguments": { "searchTerm": "Aaron" }
}

This executes the tool as if you called it directly. The response format is identical.

Intelligent Router (Shortcut)

If you're unsure which tool or category to use, skip the discovery steps and use the router:

Tool: autotask_router
Args: { "intent": "find tickets for Acme Corp" }

The router returns:

• The recommended tool name
• Pre-filled parameters based on your intent
• A description of what the tool does

Router Examples

After the router suggests a tool, use autotask_execute_tool to run it.

When to Use Each Approach

Common Category → Tool Mapping

Need to work with expenses?

Category: time_and_billing
Tools: autotask_create_expense_report, autotask_create_expense_item,
       autotask_get_expense_report, autotask_search_expense_reports

Need to build a quote?

Category: financial
Tools: autotask_create_quote, autotask_create_quote_item,
       autotask_update_quote_item, autotask_delete_quote_item,
       autotask_search_quotes, autotask_get_quote

Need to find a person?

Category: resources
Tools: autotask_search_resources

Need to log time?

Category: time_and_billing
Tools: autotask_create_time_entry, autotask_search_time_entries

Troubleshooting

Best Practices

1. Start with the router when handling a user request — it's the fastest path to the right tool
2. Cache category knowledge — once you've listed categories, you don't need to list them again in the same session
3. Use execute_tool for all calls when in lazy loading mode — don't try to call tools directly if their schemas aren't loaded
4. Fall back gracefully — if one approach doesn't work, try another (router → category listing → direct execute)

Related Skills

• Autotask API Patterns - Query building and authentication
• Autotask Tickets - Ticket management
• Autotask Expenses - Expense report management
• Autotask Quotes - Quote and line item management