Skip to main content
Glama

Idhall Delete Idea

idhall_delete_idea

Permanently deletes an initiative by its ID, removing outdated or unwanted ideas from IDhall so they no longer appear.

Instructions

Supprime définitivement une initiative (DELETE /api/v1/ideas/{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>"
    },
    "name": "idhall_delete_idea"
  }
}

Input Schema

NameRequiredDescriptionDefault
idea_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden; it does disclose the key trait that deletion is permanent ("définitivement"), which is the most important signal for a destructive operation. It stops short of stating permission requirements, whether dependent records (contributions, action plan tasks, memos) are cascaded or blocked, or whether confirmation is expected.

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 short sentence with the destructive nature and endpoint front-loaded and no wasted wording. It is tightly sized for the tool, though the endpoint string adds little for an agent that already has the name.

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

Completeness3/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, and the one-line description covers the core action. For a destructive, zero-annotation mutation, though, the absence of cascade/permission/failure behavior leaves meaningful gaps an agent would need before invoking it.

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

Parameters3/5

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

The single required parameter has 0% schema description coverage, so the description must compensate. The path template `/api/v1/ideas/{id}` implies idea_id is the idea's identifier, but nothing is said about type, format, or what happens with an unknown or already-deleted 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?

States a specific verb and resource ("Supprime définitivement une initiative") plus the underlying endpoint DELETE /api/v1/ideas/{id}, so the agent knows exactly what is removed. It does not distinguish itself from siblings like idhall_update_idea or idhall_transition_idea_stage, but the destructive framing is unambiguous.

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?

No guidance on when to use this versus alternatives (e.g. updating an idea, transitioning its stage) and no stated preconditions such as required ownership or role. The agent must infer entirely from the name and the word "définitivement" that this is the irreversible path.

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