Skip to main content
Glama

Idhall Publish Idea Draft

idhall_publish_idea_draft

Publishes an existing draft idea using its ID so it becomes a live initiative in IDhall.

Instructions

Publie une initiative brouillon existante (POST /api/v1/ideas/{id}/publish).

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

Input Schema

NameRequiredDescriptionDefault
idea_idYes
payloadNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3/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. The embedded POST route signals a mutation, but the description never says whether publishing is irreversible, whether it can be repeated, what permissions or ownership are required, or what state the idea must be in — all critical for an irreversible-looking lifecycle action.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single short sentence that front-loads the verb and resource and adds the endpoint as a locator. There is no padding or redundancy; the only flaw is that the terseness reflects missing information rather than deliberate economy.

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

Completeness4/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 described. But for a state-changing lifecycle operation with no annotations, the definition should still cover preconditions, irreversibility, and the unexplained payload parameter, which it does not.

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%, so the description must compensate. It partially does for idea_id by showing it in the path template as the identifier of the existing draft, but the payload parameter — its purpose, accepted fields, and whether it overrides draft data at publish time — is completely undocumented in both schema and description.

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 ('Publie une initiative brouillon existante') and anchors it to the HTTP route POST /api/v1/ideas/{id}/publish, so the agent knows this transitions an existing draft to published. It does not explicitly distinguish itself from siblings such as idhall_create_idea or idhall_transition_idea_stage, so differentiation is left to inference.

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 guidance beyond the word 'brouillon', no statement of preconditions (the idea must already exist and be in draft state), and no mention of alternatives for creating versus publishing an idea. The agent must infer that this is the publish step of a draft lifecycle.

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