yinxiang-mcp

create-note

Create a note in Yinxiang by providing a title and Markdown content, which automatically converts to ENML. Optionally, specify a notebook GUID to place the note.

Instructions

创建一条笔记, content 为 Markdown(自动转 ENML)。

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>",
      "content": "<content>"
    },
    "name": "create-note"
  }
}

Input Schema

Name	Required	Description
`title`	Yes	笔记标题
`content`	Yes	正文, Markdown 格式
`notebookGuid`	No	目标笔记本 guid(可选, 默认进默认笔记本)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.0Jul 30, 2026

TDQS

A3.8/5.0

Behavior3/5

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

No annotations are provided, so the description bears the burden. It discloses that content is auto-converted from Markdown to ENML, which adds behavioral context beyond the schema. However, it lacks details on success/failure behavior, required authentication, or potential 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.

Conciseness4/5

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

The description is a single sentence, concise and front-loaded with key information. It could be slightly more structured (e.g., separate sentences for purpose and special behavior), but it is adequately compact.

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?

The tool is simple with 3 parameters and no output schema. The description covers the core purpose and the Markdown conversion, but fails to mention what the tool returns (e.g., the created note object or confirmation). For a create operation, return value is important context.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100% (all 3 parameters have descriptions). The description adds value by explaining that 'content' is Markdown and will be auto-converted to ENML, which is not in the schema description. This enhances understanding beyond the bare field descriptions.

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) and resource (note), and specifies a key detail: content is Markdown auto-converted to ENML. It distinguishes from sibling tools (list-notebooks, find-notes, get-note) which are not creation tools.

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?

No explicit guidance on when to use this tool vs alternatives, nor any exclusions or prerequisites. The usage is implied (when you need to create a note), but no deeper context is provided.

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

Deploy Server