Skip to main content
Glama

Idhall Delete Action Plan Task

idhall_delete_action_plan_task

Deletes a task from an action plan by idea ID and task ID so outdated or incorrect plan items can be removed.

Instructions

Supprime une tâche d'un plan d'action (DELETE /api/v1/ideas/{id}/action-plan/tasks/{task_id}).

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": {
      "idea_id": "<idea_id>",
      "task_id": "<task_id>"
    },
    "name": "idhall_delete_action_plan_task"
  }
}

Input Schema

NameRequiredDescriptionDefault
idea_idYes
task_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.8/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full burden for a destructive mutation. It never states that the deletion is permanent/irreversible, whether required permissions or ownership apply, whether it fails if the task id does not belong to the idea, or what the response confirms — the endpoint path is the only behavioral hint.

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?

A single front-loaded sentence with no wasted wording. The embedded endpoint is somewhat redundant with the tool name but does add concrete routing information, so it earns its place.

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

Completeness3/5

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

An output schema exists, so return values need not be explained, and the operation itself is simple with only two parameters. However, for a deletion with zero annotation coverage and undocumented parameters, the absence of any irreversibility or failure-mode information leaves a real gap.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must explain both required parameters, yet it only mirrors them through the path template: '{id}' corresponds loosely to idea_id and '{task_id}' to task_id. It does not clarify that idea_id is the numeric identifier of the parent idea or how task_id is scoped to that plan.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb and resource ('Supprime une tâche d'un plan d'action') and pins the exact endpoint (DELETE /api/v1/ideas/{id}/action-plan/tasks/{task_id}), which cleanly separates it from the create/update/list action-plan-task siblings. It stops short of naming those siblings, but the delete semantics are unmistakable.

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?

There is no when-to-use or when-not-to-use guidance, and no pointer to alternatives such as idhall_update_action_plan_task for modifying a task or idhall_list_action_plan_tasks for inspecting them before removal. The usage is only implied by the tool name and the DELETE verb in the path.

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