Create a new memo in Memos using Markdown content. Set visibility, pinning, and archived state to manage your notes effectively.
Create a new memo
| Name | Required | Description | Default |
|---|---|---|---|
| state | No | Memo state: NORMAL or ARCHIVED | |
| pinned | No | Whether to pin the memo | |
| content | Yes | The memo content in Markdown format | |
| visibility | No | Visibility level: PRIVATE, PROTECTED, or PUBLIC |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are present, so the description carries the full responsibility for behavioral disclosure. It only states 'Create a new memo' and does not reveal side effects, return behavior, permission requirements, or how optional fields like visibility or pinning affect the created memo.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single concise sentence with no filler or redundant information. It states the essential purpose immediately and is appropriately sized for a simple create operation.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The schema documents all parameters, and the operation is conceptually simple, but there are no annotations and no output schema. The description does not mention what the tool returns or whether creation can fail, leaving some contextual ambiguity.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, so the parameters are already documented in the schema. The description itself adds no parameter-level meaning, which matches the baseline of 3 for high schema coverage.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description states a specific verb and resource: 'Create a new memo'. This clearly distinguishes it from sibling tools like update_memo, delete_memo, and create_attachment by action and resource type.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance is provided for when to use this tool versus alternatives. There are no exclusions, prerequisites, or comparisons to sibling tools, leaving the usage context entirely implicit.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.