Skip to main content
Glama
ThatDayneGuy

Autotask MCP Server

by ThatDayneGuy
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

autotask_create_service_call

Schedule and plan work on tickets by creating a service call with description, start and end times, optional status and company details.

Instructions

Create a new service call in Autotask. Service calls are used to schedule and plan work on tickets.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
statusNoStatus picklist ID (use autotask_get_field_info with entityType "ServiceCalls" to find valid values)
completeNoWhether this service call is complete (default: false)
companyIDNoCompany ID this service call is for
descriptionYesDescription of the service call
endDateTimeYesScheduled end date/time (ISO 8601 format)
startDateTimeYesScheduled start date/time (ISO 8601 format, e.g. 2026-03-22T09:00:00Z)
companyLocationIDNoCompany location ID (optional)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.18.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations provided. Description only says 'Create', which implies write operation but lacks details on permissions, idempotency, side effects, or success/failure behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two efficient sentences. First sentence is action, second adds context. Well front-loaded with no wasted words.

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?

No output schema and no description of return value. Lacks example, error handling, or expected outcome. Minimal completeness for a create operation.

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. Description adds no extra parameter meaning beyond schema descriptions.

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?

Clearly states 'Create a new service call' with specific resource and context. Does not explicitly differentiate from sibling tools like 'create service call ticket', but verb is distinct.

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 vs alternatives, no prerequisites or exclusions. Agent must infer usage from name alone.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools