Skip to main content
Glama
asachs01

Autotask MCP Server

autotask_create_contract

Create a new contract in Autotask by specifying required fields like company ID, name, type, category, and dates. Optionally set status, costs, and billing preferences.

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?

No annotations are provided, so the description carries full burden. It does not disclose behavioral traits like idempotency, side effects, required permissions, rate limits, or return value. Only minimal formatting info (status values, date format) is given.

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 sentences, no fluff. Each sentence adds value: purpose, field naming convention, and key format clarifications for status and dates.

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, the description is insufficient. It does not explain the return value (e.g., created contract ID), nor does it mention the need for valid picklist IDs or dependencies like company existence. Sibling tools suggest many alternatives but no differentiation is provided.

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 descriptions exist for each parameter. The tool description adds the note that 'Field names match the Autotask REST API exactly', providing context but no substantive new semantics beyond the schema.

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 'Create a new Contract in Autotask', specifying the verb and resource. It distinguishes from sibling create tools by naming 'Contract'. Additional details on field names, status values, and date format reinforce clarity.

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., update_contract, search_contracts). No prerequisites or conditions for use are mentioned, such as requiring an existing company or valid picklist IDs.

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