@damper/mcp 0.10.6 → 0.10.7

package/dist/index.js

@@ -484,15 +484,15 @@ server.registerTool('start_task', {
 server.registerTool('add_note', {
     title: 'Add Note',
     description: 'Add a note to a task. Use ONLY for non-obvious approach decisions and blockers.\n\n' +
-        '**When to use:**\n' +
-        '- Decisions: "Decision: Using X because Y"\n' +
-        '- Blockers: "Blocked: X needs Y before we can proceed"\n\n' +
         '**Do NOT use for:** Session start/end ceremony, commit logging (use `add_commit`), or restating what code changes do.\n\n' +
-        '**Formatting:** Notes are rendered as markdown. Use **bold** for key terms, `code` for technical names, and bullet lists for multiple points. ' +
-        'Start with a short bold label like **Decision:** or **Blocked:**.',
+        '**Templates** (copy and fill in):\n\n' +
+        'Decision:\n```\n**Decision:** Chose `libraryName` over `alternative` because it supports X and has fewer dependencies\n```\n\n' +
+        'Blocker:\n```\n**Blocked:** Cannot proceed with `featureName` until:\n- Dependency X is merged\n- API endpoint Y is available\n```\n\n' +
+        'Observation:\n```\n**Note:** Found that `componentName` already handles X via `methodName` — reusing instead of reimplementing\n```',
     inputSchema: z.object({
         taskId: z.string(),
-        note: z.string().describe('Markdown-formatted note. Use **bold** labels, `code` for technical terms, and bullet lists for structure.'),
+        note: z.string().describe('Markdown-formatted note. Start with a **bold label** (Decision/Blocked/Note), ' +
+            'use `code` for technical names, and bullet lists for multiple points.'),
     }),
     outputSchema: z.object({
         taskId: z.string(),

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@damper/mcp",
-  "version": "0.10.6",
+  "version": "0.10.7",
   "description": "MCP server for Damper task management",
   "author": "Damper <hello@usedamper.com>",
   "repository": {