Skip to main content
Glama

autotask_delete_quote_item

Destructive

Permanently deletes a quote item (line item) from a quote by its ID. This action is irreversible and cannot be undone.

Instructions

⚠ DESTRUCTIVE — IRREVERSIBLE. Permanently deletes a quote item (line item) from a quote. This action cannot be undone. Confirm with the user before invoking.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
quoteIdYesThe parent quote ID
quoteItemIdYesThe quote item ID to delete
Behavior4/5

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

The description adds value beyond the annotations by explicitly stating the action is irreversible and requiring user confirmation. This complements the destructiveHint: true annotation without contradiction, providing essential behavioral context for an AI agent.

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 extremely concise, using only two sentences to convey danger, action, and a safety instruction. It is front-loaded with a warning symbol and key words, making it efficient and easy to parse.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple delete operation with two parameters and clear annotations, the description covers the core behavioral aspect (irreversibility) and provides a safety prompt. It does not detail return values or side effects, but these are minimal for a delete action, so it is reasonably complete.

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?

With 100% schema description coverage, baseline is 3. The description does not add any new meaning to the parameters; both quoteId and quoteItemId are self-explanatory from their names and schema 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 'permanently deletes a quote item' and identifies the specific resource (quote item on a quote). It uses strong language like 'DESTRUCTIVE — IRREVERSIBLE' to emphasize the nature of the operation, making its purpose unambiguous even without comparison to sibling tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explicitly instructs to 'Confirm with the user before invoking,' providing a clear usage guideline. It does not mention when to avoid using the tool or suggest alternatives, but the warning sufficiently guides safe invocation.

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