Skip to main content
Glama

create_memo

Creates a flomo note from provided content; add tags inline using #tagname syntax, since tags are created implicitly by the note content.

Instructions

创建笔记。标签用 #标签名 语法写在 content 中(flomo 无独立建标签接口,标签由内容隐式创建)

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": {
      "content": "<content>"
    },
    "name": "create_memo"
  }
}

Input Schema

NameRequiredDescriptionDefault
contentYes笔记内容,支持 HTML 与 #标签名 语法

Output Schema

NameRequiredDescriptionDefault
slugYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.8/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full disclosure burden, and it does reveal a genuinely non-obvious side effect: tags are implicitly created by content rather than by an explicit call. However, it says nothing about authentication requirements, duplicate handling, content limits, or sanitization behavior, leaving meaningful gaps for a mutation tool.

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 short sentences, front-loaded with the action and followed by the one non-obvious constraint. The parenthetical justification earns its place by explaining why tags go in content.

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?

For a single-parameter create tool with an output schema already covering return values, the description supplies the essential domain quirk (implicit tag creation) that the agent could not infer elsewhere. Minor gaps around auth and duplicate behavior keep it from being fully complete.

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?

Schema coverage is 100% and the single 'content' parameter is fully described there, including HTML and #标签名 support. The description restates the same tag-syntax fact rather than adding new meaning, so the baseline 3 applies.

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 description opens with a specific verb+resource ('创建笔记'), so the agent immediately knows this creates a memo. It does not explicitly contrast with siblings like update_memo or delete_memo, but the create semantics are unambiguous.

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

Usage Guidelines4/5

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

It gives actionable guidance that tags must be embedded in content via #标签名 because flomo has no standalone tag-creation endpoint — this steers the agent away from hunting for a non-existent tool and toward the correct pattern. It does not cover when to prefer update_memo over creating a new memo, but the core usage context is clear.

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