HacknPlan MCP Server

create_from_template

Create work items in a project board using a template with custom variable substitution.

Instructions

Create work items from a template with variable substitution

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": {
      "templateName": "<templateName>"
    },
    "name": "create_from_template"
  }
}

Input Schema

Name	Required	Description
`boardId`	No	Board to add items to
`projectId`	No	The project ID (optional if HACKNPLAN_DEFAULT_PROJECT set)
`variables`	No	Template variables for substitution
`templateName`	Yes	Template name

Schema Changelog

Changes observed during successful MCP inspections.

First observedv7.2.0Jul 13, 2026

TDQS

B3.4/5.0

Behavior2/5

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

No annotations are provided, so the description must disclose behavioral traits. It only states the basic creation behavior, omitting details like whether variables are required, what happens if the template is not found, or if the operation is idempotent.

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 of 9 words, concise and front-loaded with the action. No unnecessary words.

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

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With 4 parameters (1 required), a nested object, and no output schema, the description is too brief. It doesn't mention return values, default behavior, or prerequisites, leaving the agent with gaps.

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 the schema already documents parameters. The description adds 'with variable substitution' which provides context for the 'variables' parameter, but does not add significant new meaning beyond the schema.

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 clearly states the action (create), the resource (work items from a template), and the mechanism (variable substitution). It distinguishes itself from sibling tools like create_work_items (which likely doesn't use templates).

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?

The description implies using this tool when you need to create work items from a template, but it provides no explicit when-not-to-use guidance or comparisons with alternatives like list_templates or create_work_items.

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

Deploy Server