Skip to main content
Glama

Idhall Create Idea Draft

idhall_create_idea_draft

Creates a new initiative as a draft using a required title, with optional description, plan, and extra fields, so ideas can be saved before submission.

Instructions

Crée une initiative à l'état brouillon (POST /api/v1/ideas/draft).

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": {
      "title": "<title>"
    },
    "name": "idhall_create_idea_draft"
  }
}

Input Schema

NameRequiredDescriptionDefault
planNo
titleYes
descriptionNo
extra_fieldsNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.8/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, yet it only says a draft-state entity is created and names the endpoint. It does not disclose permission/auth requirements, whether the draft is visible to other users before publication, or any side effects of draft creation.

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 key state qualifier front-loaded and zero redundant wording. Brevity here reflects under-specification rather than tight editing, but there is no structural waste.

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 described. However, for a mutation tool with no annotations and zero parameter documentation, the description should say more about the draft workflow and the meaning of the opaque inputs; it remains adequate only in the narrowest sense.

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 4 parameters (title required, plus opaque 'plan' integer and free-form 'extra_fields'), and the description adds no meaning for any of them. It does not explain what 'plan' refers to or what keys 'extra_fields' accepts, so it fails to compensate for the schema gap, though the schema's types and defaults give minimal context.

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 ('Crée une initiative') plus the resulting state ('à l'état brouillon') and the backing endpoint. This implicitly separates it from idhall_create_idea and idhall_publish_idea_draft, but it never names those siblings, so the distinction must be inferred from the word 'brouillon'.

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 explicit guidance on when to use this versus idhall_create_idea, nor any mention of the draft lifecycle (e.g. that a draft is later published via idhall_publish_idea_draft). The only hint is the word 'brouillon' in the purpose statement.

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