Skip to main content
Glama
asachs01

Autotask MCP Server

autotask_create_service_call_ticket_resource

Assign a technician to a service call ticket using ticket ID and resource ID. Optionally sets the role for the assignment.

Instructions

Assign a resource (technician) to a service call ticket.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
serviceCallTicketIDYesThe service call ticket ID to assign the resource to
resourceIDYesThe resource (technician) ID to assign
roleIDNoThe role ID for the resource on this service call (optional)

Implementation Reference

  • Input schema definition for autotask_create_service_call_ticket_resource tool. Accepts serviceCallTicketID (required), resourceID (required), and roleID (optional).
    {
      name: 'autotask_create_service_call_ticket_resource',
      description: 'Assign a resource (technician) to a service call ticket.',
      inputSchema: {
        type: 'object',
        properties: {
          serviceCallTicketID: {
            type: 'number',
            description: 'The service call ticket ID to assign the resource to'
          },
          resourceID: {
            type: 'number',
            description: 'The resource (technician) ID to assign'
          },
          roleID: {
            type: 'number',
            description: 'The role ID for the resource on this service call (optional)'
          }
        },
        required: ['serviceCallTicketID', 'resourceID']
      }
    },
  • Dispatch handler for autotask_create_service_call_ticket_resource in the tool dispatch table. Delegates to autotaskService.createServiceCallTicketResource().
    ['autotask_create_service_call_ticket_resource', async (a) => {
      const id = await s.createServiceCallTicketResource(a);
      return { result: id, message: `Successfully assigned resource to service call ticket, record ID: ${id}` };
    }],
  • Service layer method that creates a ServiceCallTicketResource record via the Autotask REST API (POST to ServiceCallTicketResources entity).
    async createServiceCallTicketResource(data: Partial<AutotaskServiceCallTicketResource>): Promise<number> {
      const http = await this.ensureClient();
      try {
        this.logger.debug('Creating service call ticket resource:', data);
        const id = await http.create('ServiceCallTicketResources', data);
        this.logger.info(`Service call ticket resource created with ID: ${id}`);
        return id;
      } catch (error) {
        this.logger.error('Failed to create service call ticket resource:', error);
        throw error;
      }
    }
  • TypeScript interface for AutotaskServiceCallTicketResource entity, with fields id, serviceCallTicketID, resourceID, and roleID.
    export interface AutotaskServiceCallTicketResource {
      id?: number;
      serviceCallTicketID?: number;
      resourceID?: number;
      roleID?: number;
      [key: string]: any;
    }
Behavior2/5

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

Without annotations, the description fails to disclose important behavioral traits, such as whether the assignment is idempotent, whether it overwrites existing assignments, or if there are any constraints like ticket status. The simple verb 'assign' implies a create action but lacks depth.

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?

The description is a single sentence that efficiently conveys the core purpose. It is front-loaded and free of fluff, though it could be slightly expanded without harming conciseness.

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?

For a mutation tool with no output schema and limited description, important contextual details are missing, such as expected return values, error conditions, and prerequisites. The description is too sparse for an agent to use reliably without additional knowledge.

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% with clear descriptions for each parameter. The tool description adds no additional value beyond the schema, so it meets the baseline of 3.

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?

The description clearly states the action ('assign a resource') and the target ('service call ticket'), distinguishing it from sibling tools like creating or deleting assignments. However, it could be slightly more explicit that it creates a new resource assignment record.

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 is provided on when to use this tool versus alternatives, such as prerequisites (ticket must exist, resource must be valid) or when not to use it (e.g., if resource is already assigned). The description lacks usage context.

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