Autotask MCP server demonstrates solid definition quality with well-structured schemas, consistent naming conventions, and detailed parameter documentation. All 6 tools have clear descriptions and comprehensive input schemas with type constraints. The server excels at parameter granularity (particularly in autotask_update_company with 25+ fields) and includes helpful field-level documentation with context about Autotask-specific conventions (e.g., invoiceTemplateID field mapping, country ID constants, tax field naming). However, output schemas are not documented in the visible source, and error handling guidance is sparse. Tool descriptions average ~90 chars, which is below the baseline (194 chars) but acceptable. Parameter descriptions are generally present and range from brief to detailed (avg ~50 chars, baseline 72 chars). Missing: explicit output schema documentation, recovery guidance for error cases, and batch operation support.

• Document output schemas for all 6 tools. Include example responses (at least JSON structure with field types and sample values) in comments or in a separate schema artifact. Specify which fields are included in search/read vs create/update responses.
• Add error handling sections to all write tools (create_company, update_company, update_company_site_configuration). Example: 'May return: duplicate_company_name (suggest verify with search), invalid_company_type (enum: 1=Customer, 2=Prospect, 3=Vendor), permission_denied (agent not authorized).'
• For autotask_update_company_site_configuration, provide a discovery pattern: 'Call autotask_get_company_site_configuration(companyID=X) to discover available field names, then invoke this tool with updates={field_name: value, ...}.' Or better yet, split into get/update with explicit field enums.
• Enhance autotask_search_companies description to state: 'Returns up to pageSize companies matching the search. Response includes companyID (for use in create_company), companyName, companyType, isActive, ownerResourceID. Use page parameter to iterate through results. Max 200 per page.'
• Add examples to billingAddress parameters: 'billToAddressToUse: Set to 1 if you want invoices sent to a different address than the company headquarters (billToCity, billToState, billToZipCode become mandatory). Set to 0 (or omit) to use regular address fields.'
• Document pagination behavior for search: 'page=1 is the first page. If you request page=999 and fewer than 999 pages exist, returns empty results (success). Recommended: start with page=1, check response count; stop iterating when response.count < pageSize.'

Inferred effective spec: 2026-07-28+.

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