Skip to main content
Glama

create_memo

Create a free-form Markdown note for ideas, plans, or general notes. Optional tags help organize content.

Instructions

Create a new memo (free-form Markdown note) in the konbu planner. Returns the created memo with its assigned UUID. Use this for notes without a due date or completion state; use create_todo for actionable tasks, and create_event for time-bound calendar items. Example: {"title":"Q3 plans","content":"## Goals\n- ship MCP","tags":["work","planning"]} → {"id":"...","title":"Q3 plans",...}. Side effects: writes a new record on each call — calling twice creates two memos. Not idempotent.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
contentNoMemo body in Markdown. Supports headings, lists, code blocks, and inline tag references such as #project. Optional.
tagsNoTag names to attach to the memo. Tags are created on-the-fly if they don't exist yet. Optional.
titleYesMemo title — short, indexed for search. Required.
Behavior5/5

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

Discloses side effects ('writes a new record on each call — calling twice creates two memos. Not idempotent.') and return value (memo with UUID). No annotations, so description carries full burden and does so thoroughly.

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 concise sentences plus an example that illustrates usage. No unnecessary 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?

Given 3 parameters (1 required) and no output schema, description covers return value details (UUID) and side effects. Complete for the tool's complexity.

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?

Input schema has 100% coverage, so baseline is 3. Description adds an example but no additional parameter details beyond schema.

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?

Clearly states 'Create a new memo (free-form Markdown note)' and distinguishes from siblings create_todo and create_event by specifying the type of content.

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

Usage Guidelines5/5

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

Explicitly advises when to use this tool ('notes without a due date or completion state') and when to use alternatives ('use create_todo for actionable tasks, and create_event for time-bound calendar items').

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/krtw00/konbu'

If you have feedback or need assistance with the MCP directory API, please join our Discord server