Skip to main content
Glama

update_memo

Update a flomo note's content by full replacement while preserving its creation time, pinned state, and attachments; fetch the original with get_memo, edit it, then write it back.

Instructions

更新笔记内容(全量替换,自动保留原创建时间/置顶状态/附件)。先 get_memo 取原内容再修改回写

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

Input Schema

NameRequiredDescriptionDefault
slugYes笔记 slug
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, the description carries the full burden, and it does disclose the key mutation traits: content is wholly replaced, while creation time, pinned status and attachments are preserved automatically. It omits other relevant behavior such as whether the overwrite is reversible, permission requirements, or confirmation needs, so the disclosure is helpful but partial.

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 compact clauses: the first declares the operation and its side effects, the second declares the required workflow. Nothing is redundant and the destructive replace semantics are front-loaded.

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 simple two-parameter mutation with a 100% covered schema and an output schema, the description covers the essential points: replacement scope, preserved fields, and the mandatory read-before-write step. Only failure mode or permission behavior is left unstated.

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 description coverage is 100%, so both parameters are already documented in the schema, including the HTML and #tag syntax for content. The description adds only the replacement/preservation context, not per-parameter meaning, which matches the baseline for fully described schemas.

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 states a specific verb and resource ('更新笔记内容') and immediately qualifies the operation as a full replacement ('全量替换'), which separates it from an incremental patch. It does not explicitly contrast with create_memo or delete_memo, so sibling differentiation is implied by the replacement semantics rather than stated.

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 an explicit ordered procedure: call get_memo first to fetch the original content, then modify and write back. That is strong prescriptive guidance. It stops short of a 5 because it never states when not to use this tool or names an alternative path for partial edits.

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