Skip to main content
Glama
asachs01

Autotask MCP Server

autotask_create_contract

Create a new service contract in Autotask with configurable terms like start/end dates, billing preferences, and estimated costs. Uses ISO date format and standard Autotask field IDs.

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

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

No annotations provided. The description adds behavioral details about status codes and date format but lacks information on permissions, side effects, success response, or error handling. Basic transparency for a create operation.

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 extremely concise (two sentences) and front-loaded with the main purpose. Every sentence provides useful information without redundancy.

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, required fields, and no output schema, the description is insufficient. It does not explain return values, validation rules, default values, or constraints (e.g., uniqueness of contract name). Leaves critical gaps for an agent to use effectively.

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 parameter meaning beyond the schema—only status and date format. Does not explain picklist IDs or interdependence of fields.

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 action (Create a new Contract), the resource (Contract in Autotask), and provides specific details about field naming, status values, and date format, distinguishing it from sibling create tools.

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 usage for creating contracts but provides no explicit guidance on when to use this tool versus other create tools like autotask_create_contract_service or autotask_create_opportunity. No alternatives or exclusions mentioned.

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