Skip to main content
Glama
Sign In
Inkdrop MCP Server

Inkdrop MCP Server

Official
by inkdropapp
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

create-note

Creates a new Markdown note in an Inkdrop notebook, letting you set its title, body, tags, and status.

Instructions

Create a new note in the database

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": {
      "bookId": "<bookId>",
      "title": "<title>",
      "body": "<body>"
    },
    "name": "create-note"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyYesThe content of the note represented with Markdown
tagsNoAn array of tag IDs to assign to the note. Call `list-tags` or `read-tag` to retrieve available tags. You can create a new tag with `create-tag` tool if necessary.
titleYesThe note title
bookIdYesThe notebook ID. Specify `template` to create a custom note template
statusNoThe status of the note

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv1.6.0
    • changedInput schema / properties / bookId / description
      Previous value: -"The notebook ID"New value: +"The notebook ID. Specify `template` to create a custom note template"
    • changedInput schema / properties / bookId / pattern
      Previous value: -"^(book:|trash$)"New value: +"^(book:|trash$|template$)"
    • addedInput schema / properties / tags / items / format
      Added value: +"starts_with"
  2. First observedv1.4.0

TDQS

C2.8/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full disclosure burden, yet it only restates the mutation. It says nothing about permissions, what object is returned, whether the note is immediately persisted/indexed, or how optional fields like status default when omitted.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One sentence with zero padding and the verb front-loaded, so there is nothing to cut. However, the brevity reads as under-specification rather than discipline for a five-parameter create tool.

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 no annotations and no output schema, the description is the only place to learn behavior and result shape, and it supplies neither. An agent still cannot tell what a successful creation returns or what constraints apply beyond the schema's field-level notes.

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 coverage is 100% – bookId documents the 'template' sentinel, tags documents the tag-ID workflow and points at list-tags/read-tag/create-tag, and body/title document format and limits. The description contributes nothing beyond this, so the 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?

States a specific verb ('Create') and resource ('a new note in the database'), so the operation is unambiguous. It does not distinguish itself from close siblings such as create-file or create-book, but the resource name carries enough differentiation for an agent to select it.

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

Usage Guidelines2/5

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

Contains no when-to-use guidance, no exclusions, and no mention of alternatives like create-file or how this relates to update-note. The reader must infer that this is the creation path for notes rather than a file or template.

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

Deploy Server

Other Tools