Skip to main content
Glama
Sign In
mcp-notes-server

mcp-notes-server

by nadimhoss
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Create note

create_note

Create a new markdown note with a title, body, and optional tags, and get back a unique slug for later reference.

Instructions

Create a new markdown note. Returns the generated slug, which is the identifier every other tool takes. Slugs are derived from the title and de-duplicated automatically.

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>",
      "body": "<body>"
    },
    "name": "create_note"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyYesMarkdown body of the note.
tagsNoLowercase topic tags used for filtering, e.g. ['recipes', 'thai'].
titleYesHuman-readable title for the note.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.5/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=false and idempotentHint=false, so the description carries the burden of explaining side effects. It discloses that a slug is generated, derived from the titlehol and de-duplicated automatically, which is beyond what annotations convey. It doesn't mention auth or rate limits, but for this simple create tool that's acceptable.

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?

Two sentences with zero fluff. The key facts (creates note, returns slug, slug derivation) are all present and front-loaded. No wasted words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Complete for a two-parameter create tool. It explains the return value (slug), its role with other tools, and the de-duplication behavior. No output schema exists, so the description carries that burden, and it does so well. Nothing an agent needs to call it correctly is missing.

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 coverage is 100% (body, title), so baseline is 3. The description adds value by explaining the relationship: slug derived from title and de-duplicated automatically. This clarifies the title parameter's role beyond its schema description. Body is straightforward.

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) on the resource (markdown note) and immediately explains the key return value (slug). It distinguishes this tool from siblings (update, delete, search, read) by focusing on creation and the slug as the identifier for other tools.

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

Usage Guidelines4/5

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

The description implies this is the creation tool and explains the slug's role as the identifier that other tools use (read, update, delete). It doesn't explicitly list alternatives or exclusion criteria, but the purpose is unmistakable from the name and description, so this is firmly a 4.

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