Skip to main content
Glama

Idhall Create Action Plan Task

idhall_create_action_plan_task

Add a task to an initiative’s action plan with details such as title, owner, phase, section, time range, and description. Use the initiative ID to record planned work through the IDhall API.

Instructions

Ajoute une tâche au plan d'action d'une initiative (POST /api/v1/ideas/{id}/action-plan/tasks).

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>",
      "title": "<title>"
    },
    "name": "idhall_create_action_plan_task"
  }
}

Input Schema

NameRequiredDescriptionDefault
ownerNo
phaseNo
titleYes
idea_idYes
sectionNo
time_rangeNo
descriptionNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/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 write operation. It conveys only that this is a POST/creation, and says nothing about required permissions, duplicate-task handling, failure modes for an invalid idea_id, or whether the task lands in a default phase/section when those fields are omitted. The presence of an output schema excuses it from describing return values, but the mutation-side behavior remains undisclosed.

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 the action first and the endpoint second; there is no filler. It is efficient, but its brevity for a seven-parameter mutation tool is a completeness problem rather than a conciseness one.

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?

With seven parameters, zero schema coverage, no annotations, and a write operation, this description is materially under-specified for the tool's complexity. The output schema covers return values, but an agent still lacks enough to fill owner/phase/section/time_range confidently or to know when calling this is appropriate.

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 seven parameters, so the description needed to compensate and does not. The only semantic link offered is the {id} placeholder implying idea_id; owner, phase, section, time_range, and description are entirely unexplained, leaving the agent to guess at their meaning and formats.

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 states a specific verb and resource ("Ajoute une tâche au plan d'action d'une initiative") and pins it to the endpoint POST /api/v1/ideas/{id}/action-plan/tasks. That is enough to separate it from the delete/update/list action-plan siblings, though the differentiation comes only from the verb rather than an explicit statement.

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_update_action_plan_task or idhall_create_idea, nor any prerequisite stated (e.g. that the idea must exist, or how a task differs from a draft/sub-idea). The endpoint path is the only contextual hint, and it must be inferred.

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