Skip to main content
Glama

Idhall Create Idea

idhall_create_idea

Create and immediately publish a new IDhall initiative with a title, target plan, and optional context or description, so teams can submit ideas directly through the API.

Instructions

Crée et publie immédiatement une nouvelle initiative dans IDhall (POST /api/v1/ideas).

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>",
      "plan": "<plan>"
    },
    "name": "idhall_create_idea"
  }
}

Input Schema

NameRequiredDescriptionDefault
planYesIdentifiant numérique de l'axe (`plan`) cible.
titleYesIntitulé de l'initiative (max 150 caractères).
contextNoContexte de l'initiative.
descriptionNoDescription de l'initiative.
extra_fieldsNoChamps additionnels optionnels (ex: targeted_sites, targeted_organizations, categories, author, etc.).

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/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. It does disclose the most important behavioral trait — the initiative is published immediately (not staged as a draft) — and identifies the underlying endpoint. It says nothing about authorization requirements, validation failures, or whether an immediately published idea can be retracted, which are material gaps for an unannotated mutation tool.

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 sentence with zero filler, front-loading the action and the immediacy constraint, followed by the endpoint as supporting detail. Nothing could be removed without losing information.

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 and parameter documentation is complete, so return values and argument meaning need not be covered. However, for a publish-on-create mutation with no annotations and a crowded sibling set including draft and publish variants, the definition should say more about side effects and routing than one sentence.

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?

Schema description coverage is 100%, so every parameter ('plan', 'title', 'context', 'description', 'extra_fields') is already documented in the schema, establishing the baseline of 3. The description adds no parameter-level meaning beyond that, mentioning neither the required fields nor the axes identifier.

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: 'Crée et publie immédiatement une nouvelle initiative dans IDhall', plus the concrete endpoint POST /api/v1/ideas. The word 'immédiatement' implicitly separates it from the draft-creating sibling idhall_create_idea_draft, but that sibling is never named, so the differentiation is only indirect.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied: 'publie immédiatement' suggests this is the one-shot create-and-publish path rather than a draft-then-publish flow, which matters given the idhall_create_idea_draft and idhall_publish_idea_draft siblings. There is no explicit when-to-use, when-not-to-use, prerequisite, or named alternative.

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