UnClick MCP Server

Promote an idea to a todo

promote_idea_to_todo

Convert an idea into a tracked todo and lock it once it has a net upvote or admin approval, linking the idea to the todo and posting a promotion event.

Instructions

Converts an idea into a tracked todo and locks the idea. Requires either net upvotes >= 1, or admin caller. Sets idea.status='locked' and idea.promoted_to_todo_id. Posts an 'idea-promoted' Boardroom event. agent_id required.

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": {
      "agent_id": "<agent_id>",
      "idea_id": "<idea_id>"
    },
    "name": "promote_idea_to_todo"
  }
}

Input Schema

Name	Required	Default
`idea_id`	Yes
`agent_id`	Yes
`priority`	No	normal
`assigned_to_agent_id`	No

Schema Changelog

Changes observed during successful MCP inspections.

Addedv0.1.5May 27, 2026

TDQS

A4/5.0

Behavior5/5

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

Beyond annotations, the description discloses significant behavior: locking the idea, setting status and promoted_to_todo_id, posting an idea-promoted event, and the authorization precondition. These details materially help an agent understand side effects.

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?

The description is compact and front-loaded: purpose first, then eligibility, side effects, event emission, and required identifier. Every sentence adds useful information without repetition.

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?

The core mutation, eligibility rule, and side effects are covered, but the description omits two optional parameters and says nothing about the return value or whether the created todo ID is surfaced. With no output schema and 0% schema coverage, those gaps matter.

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 carry parameter meaning. It only mentions agent_id explicitly and implies idea_id, while leaving priority and assigned_to_agent_id entirely unexplained, including the priority enum/default.

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

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb and resource: converts an idea into a tracked todo and locks the idea. It also names concrete state changes, making the operation clearly distinct from a generic create_todo call.

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?

It states an eligibility precondition (net upvotes >= 1 or admin caller), which gives useful usage context. However, it does not explicitly compare this tool to alternatives like create_todo or update_idea, nor does it describe when-not to use it.

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

Deploy Server