Skip to main content
Glama
asachs01

Autotask MCP Server

autotask_update_quote_item

Update quote item details such as quantity, unit price, discounts, and optional status by providing the item ID.

Instructions

Update an existing quote item (quantity, price, etc.)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
quoteItemIdYesThe quote item ID to update
quantityNoUpdated quantity
unitPriceNoUpdated unit price
unitDiscountNoUpdated per-unit discount
lineDiscountNoUpdated line discount
percentageDiscountNoUpdated percentage discount
isOptionalNoUpdated optional status
sortOrderIDNoUpdated sort order
Behavior2/5

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

No annotations are provided. The description lacks details on behavioral traits such as whether the update is partial or full, idempotency, side effects, or error handling.

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 line. While it earns its place, it could benefit from structured sections for clarity.

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?

Without an output schema, the description does not explain what the tool returns. Given 8 parameters and no behavioral details, the description is insufficient for complete understanding.

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%, so baseline is 3. The description lists example fields but adds no additional meaning beyond the schema parameter descriptions.

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 'Update an existing quote item' and provides examples of fields, distinguishing it from sibling tools like create, get, 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 explicit guidance on when to use this tool versus alternatives such as create_quote_item or delete_quote_item. No prerequisites or conditions are mentioned.

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