Skip to main content
Glama

Idhall Update Task Progress

idhall_update_task_progress

Updates an action plan task’s progress using task and idea IDs, with optional completion percentage, comment, and confidence level.

Instructions

Met à jour l'avancement d'une tâche d'un plan d'action.

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_update_task_progress"
  }
}

Input Schema

NameRequiredDescriptionDefault
commentNo
idea_idYes
percentNo
task_idYes
confidenceNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.4/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 of behavioral disclosure, yet it only says the tool 'updates progress.' It does not say whether percent is 0-100 or has an upper bound, whether omitted fields are left unchanged, whether comment and confidence are optional notes, or what permissions are required. The output schema covers the return shape, which relieves some of the pressure, but the mutation semantics remain undisclosed.

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?

The description is a single sentence with no wasted words and the mutation purpose is front-loaded. However, that brevity is the result of under-specification rather than efficiency, because nothing else was added to guide the caller.

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

Completeness1/5

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

This is a five-parameter mutation with no annotations and no schema descriptions. The description should have explained required identifiers, percent range, and optional fields, but it does not. It is inadequate for a tool of this complexity, even though an output schema exists.

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

Parameters1/5

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

There are five parameters and schema description coverage is 0%, so the schema provides no meaning for any of them. The description only implies that 'avancement' corresponds to percent and says nothing about idea_id versus task_id, comment, or confidence. This is a major documentation gap.

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: updating the progress of a task in an action plan. That is clearly distinguishable from the siblings that create, delete or list tasks, though it is not differentiated from idhall_update_action_plan_task or idhall_update_idea_implementation_progress, which sound closely related.

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 instead of idhall_update_action_plan_task or how it differs from idhall_update_idea_implementation_progress, and no statement of prerequisites such as ownership or permissions. The agent has to infer that this updates progress rather than task attributes from the name alone.

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