Skip to main content
Glama
asachs01

Autotask MCP Server

autotask_create_ticket_charge

Create a charge on a ticket to record materials, costs, or expenses with quantity, unit price, and billing information.

Instructions

Create charge on ticket for materials, costs, or expenses.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
ticketIDYesTicket ID to add the charge to
nameYesCharge name/title
descriptionNoCharge description
chargeTypeYesCharge type picklist ID (use autotask_get_field_info with entityType "TicketCharges" to find valid values)
unitQuantityNoQuantity of units
unitPriceNoPrice per unit
unitCostNoCost per unit
datePurchasedNoDate the charge was incurred (YYYY-MM-DD format)
productIDNoAssociated product ID (optional)
billingCodeIDNoBilling code ID for categorization
billableToAccountNoWhether this charge is billable to the client (default: true)
statusNoCharge status picklist ID
Behavior2/5

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

No annotations exist, so the description must carry full burden. It only says 'create charge' implying mutation, but lacks details on side effects, required permissions, or what happens to existing charges. Minimal behavioral disclosure.

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?

Single sentence, no waste. Efficient but could benefit from additional context without becoming verbose.

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 the description provides no return value info. With 12 parameters, many optional, it lacks prerequisites (e.g., ticket must exist) and expected behavior, making it incomplete for effective use.

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 each parameter described. The description adds no new meaning beyond the schema, so 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 'charge on ticket' for materials, costs, or expenses. It directly distinguishes from sibling tools like autotask_delete_ticket_charge or autotask_update_ticket_charge.

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 explicit guidance on when to use this tool versus alternatives. For example, there are sibling tools for creating time entries or expense items that could be confused, but no differentiation or context is provided.

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