note-mcp

Convert Markdown to simple note.com HTML

note_markdown_to_note_html

Convert Markdown headings, paragraphs, lists, emphasis, and links into conservative note-compatible HTML for use on note.com.

Instructions

Converts common Markdown headings, paragraphs, lists, emphasis, and links to conservative note-compatible HTML. This is a helper, not a full Markdown engine.

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": {
      "markdown": "<markdown>"
    },
    "name": "note_markdown_to_note_html"
  }
}

Input Schema

Name	Required	Description	Default
`markdown`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.1.1Aug 2, 2026

TDQS

A3.5/5.0

Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions 'conservative' and 'not a full Markdown engine,' which hints at limited handling, but it does not specify what happens with unsupported Markdown (e.g., whether it is passed through, stripped, or causes an error), nor does it describe the return format or any 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 two sentences, front-loaded with the main function and followed by a key limitation. Every sentence earns its place; there is no redundancy or filler.

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 simple tool with no output schema and no annotations, the description covers the core purpose and a significant limitation (not a full engine). However, it does not explain the return value type (e.g., HTML string) or error behavior, which would be necessary for the agent to invoke it confidently in a larger workflow.

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?

The schema has 0% description coverage, so the description must compensate. While it does not directly describe the `markdown` parameter, it implies the acceptable input by listing supported Markdown constructs (headings, paragraphs, etc.). This adds some semantic meaning beyond the raw schema, but it does not provide details on formatting, size limits, or edge-case behavior.

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 specifies a clear verb ('Converts') and resource ('Markdown to simple note.com HTML'), and lists the supported constructs (headings, paragraphs, lists, emphasis, links). It clearly distinguishes itself from sibling tools by being a helper conversion tool, none of which are converters.

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 states it is a 'helper, not a full Markdown engine,' which implies it should be used for simple conversions and not for complex Markdown. However, it does not explicitly state when to use this tool versus alternatives, nor does it provide any workflow context or exclusions beyond the limitation.

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