Skip to main content
Glama
jacob-hartmann

Quire MCP Server

quire.deleteTask

Destructive

Delete a task and all its subtasks permanently. This action cannot be undone.

Instructions

Delete a task and all its subtasks. This action cannot be undone.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
oidYesThe task OID (unique identifier) to delete
Behavior4/5

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

Annotations already indicate destructiveHint=true, so the destructive nature is known. The description adds 'This action cannot be undone' and specifies that subtasks are also deleted, which goes beyond annotations and provides useful behavioral detail.

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?

Two sentences, each essential. No unnecessary words. Front-loaded with the action and key detail (subtask deletion). Highly efficient.

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

Completeness5/5

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

For a simple destructive tool with one parameter, the description covers the action, scope, and irreversibility. No output schema needed. Complete and sufficient.

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% and the schema already describes the oid parameter as 'The task OID (unique identifier) to delete'. The tool description does not add any additional parameter meaning beyond that.

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: delete a task and all its subtasks. It uses a specific verb ('Delete') and resource ('task'), and distinguishes from other delete operations by noting subtask deletion. No ambiguity.

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 like other delete tools (e.g., deleteChat, deleteComment). No context on prerequisites or when not to use it.

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/jacob-hartmann/quire-mcp'

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