Skip to main content
Glama
ThatDayneGuy

Autotask MCP Server

by ThatDayneGuy

autotask_create_contract

Create a new contract in Autotask by specifying company, name, type, category, start and end dates, and optional details like status, fees, 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
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?

With no annotations provided, the description carries the full burden. It indicates a write operation but omits details on return value, error conditions, required permissions, or side effects. The minimal information (status values, date format) does not sufficiently disclose behavior beyond what is obvious.

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 that front-load the core purpose and essential clarifications. No redundant or unnecessary information.

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?

Given the complexity (31 parameters, no output schema, no annotations), the description is insufficient. It lacks information about the expected return value, error handling, and any prerequisites or side effects, leaving the agent underinformed for proper invocation.

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?

The input schema already describes all 31 parameters with 100% coverage. The description adds only a general note about field names matching the REST API exactly, which provides marginal added value. Baseline 3 is appropriate.

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 the resource 'Contract' within Autotask, and distinguishes from sibling tools like update_contract or create_contract_service by the verb and resource. The additional notes about field names matching the API exactly and date format provide extra 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?

The description provides no guidance on when to use this tool versus alternatives, no prerequisites, and no exclusions. The agent must infer usage from the tool name alone.

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/ThatDayneGuy/autotask-mcp'

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