Skip to main content
Glama
asachs01

Autotask MCP Server

by asachs01

autotask_update_contract

Update an existing Autotask contract by sending only the fields to change. Modify status, dates, fees, or other contract attributes with a single PATCH request.

Instructions

Update an existing Contract in Autotask (PATCH). Pass only fields you want to change; everything except id is optional. status: 1=In Effect, 0=Inactive.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesContract ID to update
statusNoContract status (1=In Effect, 0=Inactive)
endDateNoContract end date (ISO YYYY-MM-DD)
setupFeeNoSetup fee amount
companyIDNoCompany ID
contactIDNoPrimary contact ID
startDateNoContract start date (ISO YYYY-MM-DD)
descriptionNoContract description / notes
contractNameNoContract name
contractTypeNoContract type picklist ID
estimatedCostNoEstimated cost
opportunityIDNoOriginating opportunity ID
contractNumberNoExternal-facing contract number
estimatedHoursNoEstimated hours
billToCompanyIDNoBill-to company ID
contractCategoryNoContract 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
Behavior3/5

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

Reveals HTTP method (PATCH) and optionality, but lacks details on error handling, validation, side effects, or prerequisites. Since no annotations exist, more behavioral disclosure is needed.

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?

Two efficient sentences: first states action and method, second covers usage pattern and key parameter hint. No unnecessary words.

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?

Missing output schema description and prerequisite details (e.g., contract must exist). For a 32-parameter update tool, the description is moderately complete but lacks return value context.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Adds value beyond schema by explaining status mapping (1=In Effect, 0=Inactive) and the optional update pattern. With 100% schema coverage, this extra context justifies a higher score.

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 'Update an existing Contract in Autotask (PATCH)', which is a specific verb+resource combination. It distinguishes itself from sibling tools like autotask_create_contract.

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

Usage Guidelines4/5

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

Provides guidance to pass only changed fields and that everything except id is optional. Also explains status values. However, it does not explicitly mention when not to use or alternatives.

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