Skip to main content
Glama

create_note

Creates a wiki note with validated IDs, tags, links, and templates; blocks duplicate IDs unless forced and supports dry-run previews.

Instructions

새 wiki 노트 생성 — ID 충돌 시 force=True 아니면 거부. dry_run=True 시 미리보기.

안전장치: - ID 검증 (kebab-case, 한글 거부, 1-80자) - 충돌 시 force=True 아니면 거부 (기존 노트 보호) - 유사 ID 경고 (오타 감지) - dry_run=True 시 파일 미작성, 미리보기 반환 - force 덮어쓰기 시 자동 .bak 백업

Args: id: 노트 ID (kebab-case, 예: "prompt-chaining") title: 노트 제목 (한국어 가능) body: 노트 본문 (Markdown). 템플릿 사용 시 템플릿의 {{body}} 자리에 삽입됨. tags: 태그 목록 (예: ["rag", "mcp"]). 비우면 템플릿 기본 tags 사용. domain: 도메인 (지정 시 /concepts/.md). 빈 값 시 자동 추정. links: cross-link할 기존 노트 ID 목록. '## 관련 노트'(또는 템플릿 {{links}})에 추가. source_url: 출처 URL (빈 값 가능) force: True 시 동일 ID 덮어쓰기 (기본 False — 충돌 시 거부) dry_run: True 시 미리보기만 반환, 파일 미작성 (기본 False) template: 적용할 템플릿 이름 (list_templates 참고). 빈 값 시 기본 템플릿 (WIKI_DEFAULT_TEMPLATE) 사용, 그것도 없으면 템플릿 미사용.

Returns: JSON — status (ok/error/preview), path, warnings, backup

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": {
      "id": "<id>",
      "title": "<title>",
      "body": "<body>",
      "tags": "<tags>"
    },
    "name": "create_note"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
bodyYes
tagsYes
forceNo
linksNo
titleYes
domainNo
dry_runNo
templateNo
source_urlNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations provided, the description carries the full burden and does so well: it discloses ID validation rules (kebab-case, Korean rejected, 1-80 chars), collision rejection semantics, typo detection via similar-ID warnings, dry_run causing no file write, and automatic .bak backup on forced overwrite. It also states the return shape (status/path/warnings/backup). The only gap is auth or permission requirements, which are not mentioned.

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?

Front-loaded with a one-line summary followed by a safety bullet list, then Args and Returns sections — a structure that lets an agent scan the guardrails first. The only waste is duplication: force and dry_run semantics appear both in the safety list and again in Args, and the Returns block restates what the output schema already carries.

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?

For a 10-parameter mutation tool with zero annotation coverage, the definition covers the risky parts: overwrite protection, backup creation, validation constraints, and preview mode. Tool complexity is fully matched, and the return-value line is redundant only because an output schema already exists.

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

Parameters5/5

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

Schema description coverage is 0% across 10 parameters, so the description must compensate, and it does: every parameter gets meaning beyond its name — kebab-case format with an example for id, template {{body}} substitution for body, template default fallback for an empty tags list, the <domain>/concepts/<id>.md path for domain, and cross-link placement for links. Defaults and empty-value behavior are spelled out for source_url, template, domain, force, and dry_run.

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 line pairs a specific verb with a specific resource ('새 wiki 노트 생성') and immediately frames the two defining behaviors (ID collision rejection unless force, dry_run preview). It doesn't explicitly name update_note or suggest_new_note as the alternatives for editing or drafting, so an agent must infer the boundary from the word '새' (new).

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 implied through behavior rather than stated: '기존 노트 보호' signals that existing notes should be modified elsewhere, and 'template: ... (list_templates 참고)' routes the agent to a sibling for template discovery. There is no explicit when-to-use/when-not sentence, e.g. 'for edits to an existing note use update_note instead', and no stated prerequisites.

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