Skip to main content
Glama

autotask_create_contract

Create a new contract in Autotask by providing required fields: company ID, contract name, type, category, start date, and end date. Supports optional settings for billing, costs, SLA, and status.

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
Behavior2/5

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

With no annotations, the description bears full burden. It only mentions field mapping and date/status conventions, but does not disclose side effects, authorization needs, or response structure. Agent cannot infer that creation is destructive or requires specific permissions.

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?

Three concise sentences, front-loaded with purpose. No redundant information. Efficient and well-structured.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given 31 parameters and no output schema, the description omits return value (e.g., contract ID). It covers core details but lacks completeness for agent to predict behavior fully.

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?

Input schema has 100% coverage, so description adds little beyond schema descriptions. It clarifies status values (1/0) and date format, but these are partially covered in schema. Baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Description clearly states the action (create) and resource (contract), with additional details like field names matching API and date format. However, it does not differentiate from sibling tools like autotask_create_contract_service.

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 guidance on when to use this tool versus alternatives (e.g., autotask_update_contract). No prerequisites 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/wyre-technology/autotask-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server