Skip to main content
Glama

notes_create

Record research findings, decision records, meeting summaries, and other long-form artifacts. Each note is auto-tagged as agent-created and can be associated with a plan for context.

Instructions

Create a work note -- a research finding, decision record, meeting summary, or any artifact long enough to deserve its own file. Auto-tagged created-by:agent. Notes carry the long form; memory_write carries the compact durable knowledge a future session must not miss, so put the write-up here and the one-line lesson there rather than duplicating either. Pass plan= when the note is a plan's narrative or supporting context, so it joins that plan's composition beside its tasks. Do not use this for what the repo, AGENTS.md/CLAUDE.md, or the current conversation already records, and use notes_append to extend an existing note rather than creating a near-duplicate of it.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bodyYesmarkdown body (aliases: content, text)
planNooptional plan slug (plan:<slug> convention): tags this note into that plan's composition so it surfaces on the Plans screen alongside its tasks_add plan=<slug> steps. Use it whenever this note is a plan's narrative or supporting context.
tagsNotags (a comma-separated string is also accepted)
titleYesnote title
projectNoproject slug; defaults to the bound/ambient session's project. An unknown slug CREATES that project -- naming a new one is normal and never an error. Pass project=global ONLY for knowledge that belongs in EVERY project's briefing; it is not a neutral default. With no session and no explicit project the call is rejected as ambiguous.
source_urlNooptional source URL
descriptionNooptional one-line summary
Behavior4/5

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

Describes auto-tagging behavior and mutation (create). Explains project parameter default and creation of new projects on unknown slug. No annotations to contradict; description adds useful behavioral context beyond raw schema.

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?

Single paragraph with essential information front-loaded: purpose, auto-tag, sibling differentiation, and usage guidance. Each sentence contributes meaning; could be slightly shorter but is well-organized.

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?

Covers key aspects: purpose, sibling distinctions, parameter guidance, and behavioral traits. Lacks mention of return value or error handling beyond missing session, but given no output schema, the description is adequate for agent selection.

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%, but description adds value by clarifying plan parameter's role in plan composition and project parameter's default and special 'global' value. Other parameters are straightforward; no extra semantics needed.

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?

Defines tool as creating work notes for specific purposes (research finding, decision record, meeting summary) and distinguishes from memory_write (compact knowledge) and notes_append (extending existing notes). Exclusive purpose is clear.

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 states when to use this tool (long-form artifacts) and when not to use (repo, AGENTS.md, current conversation). Directs to use notes_append for extensions and memory_write for one-line lessons. Provides context for plan parameter.

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/0spoon/seamless'

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