Skip to main content
Glama
asachs01

Autotask MCP Server

autotask_create_expense_item

Creates a new expense item on a given expense report, specifying amount, date, category, and optional billable/reimbursable flags.

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
Behavior2/5

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

No annotations are provided, so the description must reveal key behavioral traits. It only states the core action without explaining what the tool returns, whether it is idempotent, or if the parent expense report must exist. Minimal behavioral context.

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 with no unnecessary words. It is concise but could incorporate more useful information without harming brevity.

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 no output schema, 10 parameters, and no annotations, the description lacks essential context such as return value, error handling, and usage prerequisites. It is insufficient for an agent to fully understand the tool's behavior.

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?

The input schema covers all 10 parameters with descriptions, achieving 100% coverage. The description adds no extra meaning beyond the schema. Baseline 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 action (create) and the resource (expense item on an existing expense report). It differentiates from sibling tools like 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?

The description provides no guidance on when to use this tool versus alternatives, such as autotask_create_expense_report. It does not mention prerequisites like the requirement that the expense report already exists.

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