Skip to main content
Glama

Create

create

Creates a note, a folder or an app. A note: path "Work/Acme.md" (its name is its title; folders are made as needed; with no folder it goes in the first folder, usually Notes) and content, its markdown. In a note's folder ("Work/Acme/Agenda.md") it becomes that note's sub-note. A folder: path "Work/Clients/". An app: path is the note that becomes the app (existing, or new like "Work/Habits.md"); it starts as a React + TypeScript + Tailwind + shadcn/ui project whose README.md says how apps run here, or, with template, as that pintonotes.com template's app, its data and its note. Notes are markdown: checklists "- [ ] item", links to notes [[Title]], and a tracker is a table with a line like above it (keep values in range).

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": {
      "path": "<path>"
    },
    "name": "create"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYesWhere: "Work/Acme.md", "Work/Clients/", or the app's note.
typeNoDefault note.
pinnedNo
contentNoA note's markdown.
templateNoAn app: start from this template's app, data and note (its name, as in pintonotes.com/templates/habit-tracker).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / template
      Added value: +{
      +  "description": "An app: start from this template's app, data and note (its name, as in pintonotes.com/templates/habit-tracker).",
      +  "type": "string"
      +}
  2. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations declare a safe, non-destructive, non-open-world write, and the description adds genuinely non-obvious behavior on top: folders are created as needed, a pathless note lands in the first folder (usually Notes), a path inside a note's folder becomes a sub-note, and an app is scaffolded as a React + TypeScript + Tailwind + shadcn/ui project. It does not say what is returned or whether an existing path is overwritten or errored, so it stops short of 5.

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?

The lead is front-loaded and correctly ordered (verb, then per-type clauses), but it is a single dense paragraph whose parenthetical asides stack several rules at once. The trailing markdown/mini-DSL guidance (checklists, [[links]], pane-table directives) is boundary-line material for a create tool and makes the definition heavy to scan.

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

Completeness4/5

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

With no output schema, the description ideally would say what a successful create yields, and it does not — a real gap for an agent that needs the resulting path or identifier. Otherwise it is complete for a 5-parameter creation tool: side effects, defaults, substitution rules, and content format are all covered.

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 80%, so the schema already carries much of the load, but the description goes further: `path` semantics shift by type, a note's filename is its title, `content` is markdown, and `template` is named as a pintonotes.com template slug. That is meaningful clarification beyond the schema's one-line hints.

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 opening sentence names a specific verb (creates) and the three resources it can create (note, folder, app), then dedicates a clause to each mode, so an agent can map its intent to the right `type`. It does not differentiate itself from siblings such as `write` or `edit`, which would be the remaining step for a 5.

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: the path examples ("Work/Acme.md" vs "Work/Clients/" vs a note that becomes an app) effectively tell the agent which mode to pick, but nothing says when to use this tool instead of `write`, `edit`, or `move`. There are also no stated exclusions or prerequisites.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.