Skip to main content
Glama

Idhall Update Idea Implementation Progress

idhall_update_idea_implementation_progress

Update an initiative's implementation progress by recording completion percentage, confidence level, and an optional comment against its idea ID.

Instructions

Met à jour l'état d'avancement de la mise en œuvre 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_update_idea_implementation_progress"
  }
}

Input Schema

NameRequiredDescriptionDefault
commentNo
idea_idYes
percentNo
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 provided, so the description carries the full burden of behavioral disclosure. It conveys only that a mutation happens; it says nothing about permissions required, whether values are overwritten or appended, how percent and confidence interact, or what happens when optional fields are omitted.

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?

A single sentence with no filler, so nothing is wasted. But the brevity is under-specification rather than economy: the one sentence does not carry enough information for an agent to act on.

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?

An output schema exists, so return values need not be explained. Still, for a mutation tool with no annotations and four undocumented parameters, the definition is well short of what an agent needs to invoke it reliably.

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 four parameters, so the description must compensate and largely fails. It hints at a progress state but gives no meaning for percent (scale/units), confidence (free string? expected values?), comment, or the required idea_id.

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

Purpose3/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 implementation progress state of an initiative), so the intent is recognizable. However, it does not distinguish this from close siblings such as idhall_update_task_progress or idhall_update_idea, nor does it clarify what 'état d'avancement' actually comprises (percent, confidence, comment).

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 the sibling progress/update tools, and no prerequisites or exclusions are stated. The only usage signal is implied by the tool name and the single sentence.

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