Skip to main content
Glama
ThatDayneGuy

Autotask MCP Server

by ThatDayneGuy

autotask_create_ticket_charge

Create a charge on a ticket for materials, costs, or expenses by specifying ticket ID, name, and charge type.

Instructions

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

Input Schema

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

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

The description does not disclose behavioral traits such as whether it mutates data, if it's idempotent, permission requirements, or error conditions. With no annotations, the description bears full responsibility and fails to provide adequate transparency.

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 extremely concise at one short sentence. While it is not verbose, it sacrifices critical detail. It earns a 4 for being efficient but could be improved by adding more context without becoming wordy.

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 12 parameters, no output schema, and no annotations, the description is insufficient. It does not explain return values, how parameters like chargeType should be used (though schema references get_field_info), or any post-condition effects. Completeness is low.

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 description coverage is 100%, so the baseline is 3. The description adds no additional meaning beyond the schema; it merely summarizes the purpose. No extra value is provided for understanding parameter usage.

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', and specifies the context 'on ticket for materials, costs, or expenses'. It effectively distinguishes from sibling tools like update, delete, and search.

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 information is provided about when to use this tool versus alternatives, prerequisites, or scenarios where it should not be used. Siblings like update and delete are present but no differentiation guidance.

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