This server demonstrates solid tool definition quality with consistent verb-based naming, explicit JSON Schema for all parameters, and clear descriptions for most tools. All 6 tools follow the pattern of action_resource naming (autotask_[verb]_[noun]). Parameter schemas are well-formed with types, constraints (min/max for pagination), and descriptions. However, there are gaps: parameter descriptions are sometimes sparse (e.g., autotask_test_connection has no parameters to describe), some tools lack output schema documentation, and error handling guidance is not visible in the definitions. The server excels in schema rigor but falls short in LLM-optimization of descriptions and output documentation.

• Document output schemas for all tools. For autotask_search_companies, specify: {companies: [{id: number, companyName: string, isActive: boolean, ...}], pageSize: number, totalCount: number}. For create/update operations, document returned ID and any fields the agent may need for follow-up calls.
• Add examples of valid picklist IDs (e.g., invoiceTemplateID: 103=Due on Receipt, 104=NET 30) directly in parameter descriptions so LLMs understand the mapping without extra discovery calls.
• Expand autotask_update_company_site_configuration description: 'Update custom tenant-defined fields on a company site configuration. Common uses include facility location, support tier, or deployment details. Query autotask_get_company_site_configuration first to discover available fields for your tenant.'
• Add a discovery/reference tool (e.g., autotask_list_picklists or autotask_describe_company_schema) that returns valid values for all enum-like fields. This is especially important for companyType, classification, and invoiceTemplateID, where LLMs cannot guess valid IDs.
• For autotask_update_company, split the 24 parameters into logical groups in the description or provide a link to field mappings. Alternative: offer multiple focused tools (update_company_billing, update_company_invoicing) to reduce cognitive load.
• Add error recovery hints: 'If search returns 0 results, the company may be inactive. Use isActive=false to include inactive records, or check the spelling of searchTerm.'
• Include pagination guidance in autotask_search_companies description: 'Returns max 200 companies per page. Use page and pageSize to iterate. totalCount indicates how many records match your search.'

Inferred effective spec: 2026-07-28+.

• Relies on Logging (deprecated) - log to stderr or use OpenTelemetry