Skip to main content
Glama
haxos-anon

Autotask MCP Server

by haxos-anon
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

autotask_create_company

Create a new company in Autotask by providing required details like company name and type. Supports optional fields such as phone, address, and owner to streamline client onboarding.

Instructions

Create a new company in Autotask

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
companyNameYesCompany name
companyTypeYesCompany type ID
phoneNoCompany phone number
address1NoCompany address line 1
cityNoCompany city
stateNoCompany state/province
postalCodeNoCompany postal/ZIP code
ownerResourceIDNoOwner resource ID
isActiveNoWhether the company is active

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.18.0

TDQS

B3.1/5.0
Behavior2/5

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

No annotations provided, so the description should disclose behavioral traits like mutability, permissions, or error handling. It only states 'create' without any additional context, leaving gaps for a mutation tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Extremely concise at 6 words, but lacks structure or additional helpful details. It is not verbose, but the brevity sacrifices value.

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?

With 9 parameters and no output schema, the description fails to explain expected outcomes (e.g., returned company ID) or critical context like valid companyType values. Incomplete for a creation tool.

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

Parameters3/5

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

Schema description coverage is 100%, so the schema already documents all parameters clearly. The description adds no extra meaning beyond what is in the schema, meeting the baseline.

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 specifies the action (create), resource (company), and system (Autotask), distinguishing it from sibling tools like autotask_create_contact or autotask_create_ticket.

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 guidelines on when to use this tool, prerequisites (e.g., needing a valid companyType ID), or alternatives. The description is minimal without usage context.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools