Skip to main content
Glama

Idhall List Action Plan Tasks

idhall_list_action_plan_tasks

Lists action plan tasks for a specific initiative, enabling review and tracking of planned work.

Instructions

Liste les tâches du plan d'action d'une initiative.

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

Input Schema

NameRequiredDescriptionDefault
propsNo
idea_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 supplied, so the description carries the full behavioral burden, yet it discloses nothing about permissions, pagination, result ordering, or whether the listing is filtered. The existence of an output schema offsets the need to describe return values, but the operational behavior remains opaque.

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 zero waste, but its brevity reflects under-specification rather than disciplined conciseness. A short clause on the idea_id scoping or result shape would cost little and add real value.

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 simple list tool with no annotations and zero parameter documentation, the description does too little: the required scope key and the optional props argument are both undocumented. The output schema covers the return side, but the invocation side is incomplete.

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% for both parameters, so the description would need to compensate and it does not. The required idea_id and the unexplained 'props' array are never mentioned, leaving the agent to guess that the listing is keyed by an initiative ID.

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 ('Liste les tâches du plan d'action') scoped to one initiative, which clearly separates it from sibling mutation tools like idhall_create_action_plan_task or idhall_delete_action_plan_task. It stops short of naming any sibling or alternative, so the differentiation is implied rather than explicit.

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?

The description gives no when-to-use context, no prerequisites, and no mention of alternatives such as idhall_list_ideas or the task-mutation siblings. An agent must infer that this is the read path for tasks belonging to a single initiative from the wording alone.

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