NoteKing MCP

noteking_create_note

Creates a new Markdown note under a project or as a standalone scratchpad, with options for title, body content, pinning, and pinned ordering. Use it to capture developer notes, ADRs, or quick ideas.

Instructions

Create a new Markdown note in NoteKing (under a project or as a standalone scratchpad note)

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": "noteking_create_note"
  }
}

Input Schema

Name	Required	Description
`body`	No	Raw Markdown content of the note
`title`	Yes	Title of the note
`pinned`	No	Whether the note should be pinned to the NoteKing sidebar
`project_id`	No	Associated project ID, or null for a standalone scratchpad note
`pinned_position`	No	Sequential ordering position among pinned notes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Nov 14, 2026

TDQS

B3.2/5.0

Behavior2/5

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

No annotations are supplied, so the description carries the entire burden. It discloses the two creation modes but says nothing about side effects, permission/auth requirements, title uniqueness, default body handling, or whether the created note's identifier is returned for follow-up calls such as append_to_note.

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 front-loaded sentence with no filler. The parenthetical clause is compact and informative rather than redundant, though it slightly muddies the core action statement.

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?

For a five-parameter creation tool with no annotations and no output schema, the definition covers the core action and placement modes but leaves a real gap: what the call returns (notably the new note's id) and how pinned/pinned_position interact. Adequate but not fully self-sufficient.

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 (body, title, pinned, project_id, pinned_position) is already documented in the schema. The description's only added meaning is the project-vs-scratchpad framing, which the project_id schema text also states, so baseline 3 applies.

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 pairs a specific verb ("Create") with a specific resource ("a new Markdown note in NoteKing") and states the two placement modes (project vs. standalone scratchpad). The word "new" implicitly separates it from noteking_append_to_note and noteking_update_note, though no sibling is named.

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: an agent can infer this is the tool for creating rather than modifying notes, and the parenthetical hints at project vs. scratchpad selection. There is no explicit when-to-use/when-not guidance and no named alternative for adding content to an existing note.

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

Deploy Server