Skip to main content
Glama
asachs01

Autotask MCP Server

by asachs01

autotask_create_contract

Creates a new contract in Autotask by specifying required fields like company ID, contract name, type, category, start and end dates. Optionally set status, billing, and financial parameters.

Instructions

Create a new Contract in Autotask. Field names match the Autotask REST API exactly. status: 1=In Effect, 0=Inactive. Dates are ISO format (YYYY-MM-DD).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
statusNoContract status (1=In Effect, 0=Inactive)
endDateYesContract end date (ISO YYYY-MM-DD)
setupFeeNoSetup fee amount
companyIDYesCompany ID the contract is associated with
contactIDNoPrimary contact ID for the contract
startDateYesContract start date (ISO YYYY-MM-DD)
descriptionNoContract description / notes
contractNameYesContract name
contractTypeYesContract type picklist ID
estimatedCostNoEstimated cost
opportunityIDNoOriginating opportunity ID
contractNumberNoExternal-facing contract number
estimatedHoursNoEstimated hours
billToCompanyIDNoBill-to company ID
contractCategoryYesContract category picklist ID
estimatedRevenueNoEstimated revenue
billingPreferenceNoBilling preference picklist ID
isDefaultContractNoWhether this is the default contract for the company
renewedContractIDNoID of the contract this renewed
contractPeriodTypeNoPeriod type picklist ID
overageBillingRateNoOverage billing rate
exclusionContractIDNoExclusion contract ID
purchaseOrderNumberNoCustomer purchase order number
setupFeeBillingCodeIDNoBilling code ID for the setup fee
billToCompanyContactIDNoBill-to contact ID
contractExclusionSetIDNoContract exclusion set ID
serviceLevelAgreementIDNoSLA ID
internalCurrencySetupFeeNoSetup fee in internal currency
organizationalLevelAssociationIDNoOrg level association ID
internalCurrencyOverageBillingRateNoOverage rate in internal currency
timeReportingRequiresStartAndStopTimesNoWhether time entries require start/stop times
Behavior2/5

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

No annotations are provided, so the description must cover behavioral traits. It only notes field mappings and date formats, omitting side effects, authorization needs, error handling, and return values.

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?

The description is three short, front-loaded sentences with no extraneous information, achieving high conciseness.

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 31 parameters and no output schema or annotations, the description is too sparse to be complete. It lacks explanation of return values, error scenarios, and complex parameter relationships.

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 coverage is 100%, so baseline is 3. The description adds minimal value by reiterating date formats and status mappings already in the schema, providing no further semantic enrichment.

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 the verb (create) and resource (Contract in Autotask), distinguishing it from sibling tools like autotask_search_contracts and autotask_update_contract.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies using this tool to create a contract but provides no explicit guidance on when to use it vs. alternatives, no prerequisites, and no exclusions.

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