Skip to main content
Glama
asachs01

Autotask MCP Server

autotask_create_expense_item

Create an expense item on an existing expense report with required details: description, date, category, amount.

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?

With no annotations, the description should disclose behavioral traits such as destruction, authorization needs, or side effects. However, the description only states the basic action without any additional behavioral context. No contradiction with annotations exists since none are provided.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single concise sentence that efficiently conveys the tool's purpose without any unnecessary words or extraneous information.

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 the complexity (10 parameters, 5 required, no output schema, no annotations), the description is insufficient. It fails to explain return values, success/failure behavior, or any constraints beyond what is in the schema.

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 all parameters. The description adds no extra meaning beyond what is in the schema, hence baseline score of 3.

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 'Create an expense item on an existing expense report' clearly states the action (create), the resource (expense item), and the parent entity (expense report). This effectively distinguishes it from sibling tools like autotask_create_expense_report and other create tools.

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 usage guidance is provided. The description does not specify when to use this tool versus other expense-related tools, nor does it mention prerequisites like having a valid expenseReportId or any constraints.

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