Skip to main content
Glama

autotask_create_expense_item

Adds an expense line item to an existing expense report in Autotask PSA. Specify details like category, amount, and date.

Instructions

Create an expense item on an existing expense report

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
expenseReportIdYesThe expense report ID to add the item to
descriptionYesLine item description
expenseDateYesDate of expense (YYYY-MM-DD format)
expenseCategoryYesExpense category picklist ID
amountYesExpense amount
companyIdNoAssociated company ID (0 for internal)
haveReceiptNoWhether a receipt is attached
isBillableToCompanyNoWhether billable to company
isReimbursableNoWhether this expense is reimbursable
paymentTypeNoPayment type picklist ID
Behavior1/5

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

No annotations provided, so description carries full burden. Only 'Create' is stated, with no disclosure of side effects, required permissions, or error conditions. Fails to describe what happens after creation.

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, front-loaded with verb and resource. No wasted words, but could be expanded slightly 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?

With 10 parameters, no output schema, and no annotations, the minimal description fails to provide complete context. Missing details like return value, editable status requirement, or item confirmation.

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 schema already describes each parameter. The tool description adds no additional meaning beyond what is in the schema, so baseline score of 3 applies.

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', the resource 'expense item', and the context 'on an existing expense report'. It distinguishes from sibling tool autotask_create_expense_report which creates the report itself.

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 versus alternatives. It does not mention prerequisites such as requiring an existing expense report ID, or any conditions like report status.

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/wyre-technology/autotask-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server