Skip to main content
Glama

Idhall Update Action Plan Task

idhall_update_action_plan_task

Update a single task in an idea's action plan by patching specified fields through the IDhall API, so you can revise task details without rebuilding the plan.

Instructions

Modifie une tâche d'un plan d'action (PATCH /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>",
      "fields": "<fields>"
    },
    "name": "idhall_update_action_plan_task"
  }
}

Input Schema

NameRequiredDescriptionDefault
fieldsYes
idea_idYes
task_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.6/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden, and it discloses almost nothing: no statement of whether unspecified fields are preserved, whether changes are reversible, what authorization is required, or how validation failures surface. Only the HTTP method implies mutation, which the agent could already guess from the name.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is a single front-loaded sentence with no filler, which is structurally clean. However, the brevity is achieved by omission rather than economy, since the sentence conveys essentially only the endpoint and nothing the schema does not already show.

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?

For a mutation tool with a nested free-form payload and zero annotation coverage, the definition leaves the most important question unanswered: what goes inside 'fields'. The presence of an output schema excuses explaining return values, but not the missing description of writable fields and update semantics.

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% across three required parameters, and the description only implicitly maps idea_id and task_id through the URL template. The critical parameter, 'fields', is a free-form object with additionalProperties: true and is given no explanation of accepted keys, nesting, or value types anywhere in the definition.

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 ('Modifie') and resource ('une tâche d'un plan d'action') and backs it with the exact endpoint PATCH /api/v1/ideas/{id}/action-plan/tasks/{task_id}, which unambiguously separates it from the create/delete/list task siblings. It stops short of naming those siblings explicitly, so differentiation is inferential rather than stated.

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 guidance on when to use this tool versus idhall_create_action_plan_task, idhall_delete_action_plan_task, or idhall_update_task_progress, nor any statement of prerequisites, permissions, or when a caller should not use it. The PATCH path hints at partial-update semantics but that is left for the agent to infer.

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