Skip to main content
Glama

Delete subtask

delete_subtask
DestructiveIdempotent

Soft-delete a billing subtask and its time entries into the recycle bin, where an admin can restore them together. Returns a preview unless confirm=true is set.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "subtask_id": "<subtask_id>"
    },
    "name": "delete_subtask"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmNoSet true to perform the action. Omit or false returns a preview only — nothing is written.
subtask_idYesId of the subtask to delete.
idempotency_keyNoOptional caller-supplied key; retrying with the same key returns the original result instead of acting twice.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Goes well beyond the annotations by disclosing that this is a soft delete into a recycle bin, that time entries are cascaded, that an admin can restore the subtask and entries together, and that nothing is written unless confirm=true. The annotations only flag destructive/idempotent; the description supplies the recoverability and blast-radius context that actually matters here.

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, zero waste, with the destructive action and its scope front-loaded before the preview/confirm condition. Every clause carries decision-relevant information.

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 cascading mutation with no output schema, the description covers what is affected, where it goes, whether it is recoverable, and when it actually executes. It stops short of describing what the returned preview contains or what permissions are required to restore, but nothing needed to call it correctly is missing.

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 documents confirm's preview behavior and idempotency_key's retry semantics. The description restates the confirm gating but adds no syntax or format detail beyond what the schema provides, so the baseline of 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?

States a specific verb and resource ("soft-delete a billing subtask") plus the cascade scope ("and its time entries"), which distinguishes it behaviorally from hard-delete siblings such as permanent_delete_entity. An agent knows exactly what this does without opening the schema.

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?

Gives clear operational guidance on the preview-vs-execute path via confirm=true, which is the key decision an agent must make before calling. It does not explicitly name when to pick this over a permanent deletion sibling, leaving that inference to the agent.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources